Managing a fleet of devices

ABSTRACT

Methods of managing a fleet of devices are provided, as are methods for configuring a standby device for a job in a workflow environment, and methods for performing a job in a workflow environment. Device information is analyzed, such as information pertaining to verification systems. Device instructions are sent to various locations on a device network in response to a deviation from a parameter value having been detected. The deviation from the parameter value may correspond to printed media and/or indicia produced by one or more devices. A workflow device and a standby device are provided, and the workflow device sends configuration data to the standby device. The standby device installs configuration data and is introduced into the workflow environment.

FIELD OF THE INVENTION

The present disclosure relates to systems and methods for managing afleet of devices, for example, one or more devices that have beendeployed in a workflow environment. More particularly, but withoutlimitation, the present disclosure concerns systems and methods fordeploying devices in a workflow environment and assigning jobs to thosedevices, for managing performance objectives, for introducing a standbydevice into a workflow environment, and for performing jobs in aworkflow environment. Further, these methods generally allow users tomanage a fleet of devices without requiring much knowledge or skillpertaining to information technology.

BACKGROUND

It is common for a fleet of devices to be deployed in a workflowenvironment. In some settings, a fleet of devices may be deployed acrossa large enterprise, which may include numerous workflow environmentsand/or numerous devices within a given workflow environment. Managing alarge fleet of devices presents several challenges which are addressedby the present disclosure.

For instance, there are numerous examples of workflow environments whichrequire outputs that meet a certain level of quality, productivity,and/or cost-efficiency. The quality of outputs from a given device canbe managed to some degree by periodically sampling outputs and testingthe samples for various quality parameters, and then taking appropriateaction when the test results indicate an issue with output quality.However, in some settings, quality issues may go undetected for sometime and/or quality issues may be unanticipated, for example, whenoutputs are only periodically sampled for quality testing. Qualityissues that go undetected may lead to further undesirable outcomes, suchas unsalable or unusable outputs, rework, downtime for devices, customercomplaints, and the like. In some situations, an issue with outputquality may require downtime for a workflow device until the issue hasbeen resolved. Further, quality issues that are unanticipated may leadto delayed responses. Delays in detecting and responding to outputquality, as well as downtime for a workflow device, tend to directlyimpact the uptime and productivity, and correspondingly the operatingcosts and profitability, of a device, a workflow environment, and/or anenterprise. It would therefore be advantageous to provide improvedmethods for managing output quality for a device or fleet of devices,including detecting or predicting quality issues, managing undesirableoutcomes from quality issues, and timely responding to quality issues.

As another example, a multitude of factors may cause the time whenmaintenance or service is required for a given device to vary as betweendifferent devices and/or as between different workflow environments. Insome situations, maintenance or service requirements for devices may goundetected for some time and/or such requirements may be unanticipated.If a device goes too long without maintenance or service, the device mayexperience a failure or performance or quality issues may arise; but onthe other hand, if maintenance or service is performed too frequently,costs will be incurred that may otherwise have been avoidable. Likewise,a device failure may occur unexpectedly, and eventually a device willreach the end of its useful life. It would therefore be advantageous toprovide improved methods for managing maintenance or service, forresponding to failures, and for managing useful life, of a device orfleet of devices, including managing maintenance or service schedules,detecting or predicting maintenance or service issues, and timelyresponding to such issues.

As another example, in some situations, a given output may be produciblewith any one or more different devices. Similarly, in some situations, agiven device may be configurable with any one or more differentconfigurations. Such configurations may include a selection of componentparts, consumables, and settings for the device. Operations of anenterprise, a workflow environment, or a given device may be affected bythe selection of a device and/or by the selection of a configuration fora device. For example, such sections may impact output quality,maintenance or service requirements, uptime, productivity, and/oroperating costs, of a device, a workflow environment, and/or anenterprise. However, in some situations a multitude of factors may berelevant, and/or the relevance of various factors or the significance ofvarious factors may vary as between different devices and/or as betweendifferent workflow environments. Furthermore, in some situations,various performance objectives may be inversely proportional to oneanother (e.g., quality vs. cost, quality vs. productivity, productivityvs. cost), such that tradeoffs between competing objectives may exist.It would therefore be advantageous to provide improved methods formanaging the selection of devices and/or device configurations,including managing performance objectives, and deployment of devicesand/or device configurations into workflow environments, and assignmentof jobs to various devices.

These issues are especially magnified when managing an enterprise thatutilizes a large number of workflow devices and/or multiple workflowenvironments. It would therefore be advantageous to provide improvedsystems and methods for managing a large fleet of devices, in particularbut without limitation, fleets of devices across an enterprise havingmultiple workflow environments.

The present disclosure seeks to address the foregoing shortcomings andneeds, for example, by providing systems and methods that utilizedevices having a verification system which allows for improvedmonitoring of output parameters, which output parameters may then beutilized in the systems and methods for managing fleets of devicesdisclosed herein, including, without limitation, systems and methods formanaging performance objectives, systems and methods for managingmaintenance and service requirements, systems and methods for managingthe selection of devices device configurations, and/or systems andmethods for deploying or introducing devices into workflow environments.

In addition to output quality, there are numerous examples of workflowenvironments which require a high level of uptime or productivity. Assuch it would be desirable to enhance the uptime or productivity of adevice or a fleet of devices in a workflow environment by providing oneor more standby devices, which can be introduced into the workflowenvironment when a workflow device experiences a failure, a qualityissue, or otherwise removed from service for some reason. Similarly, itwould be desirable to enhance uptime or productivity by providing one ormore standby devices which can be introduced into the workflowenvironment in connection with improved methods for managing theselection of devices and/or device configurations, for example, butwithout limitation, in connection with managing performance objectives.

When introducing a standby device into a workflow environment in placeof a workflow device, generally the standby device may require firmware,software, applications, and/or settings identical to or compatible withthe workflow device being replaced. In some situations, a fleet ofdevices may comprise several workflow devices having various differentconfigurations, including different firmware, software, applications,and/or settings. For example, different configurations may be desirableto configure devices for various different jobs or users. Additionally,in some situations different configurations may be required as betweendiffering device models in order to configure each of them to perform agiven job in a workflow environment, and/or different configurations maybe desirable for managing performance objectives.

In some workflow environments, there may be a large number of workflowdevices that need to be managed, and some enterprises may encompassmultiple workflow environments. Accordingly, some workflow environmentsmay have multiple different devices with multiple differentconfigurations. Such multiple different devices and/or multipledifferent configurations may require various differing combinations offirmware, software, applications, and/or settings, which may becomeburdensome to manage. Oftentimes, it would be impractical to maintain aseparate standby device for each different workflow device or for eachdifferent configuration. For example, it may be cost prohibitive tomaintain a large number of standby devices. Instead, it would bedesirable to maintain an optimally small number of standby devices,preferably having a given standby device configurable to perform variousdifferent jobs corresponding to several different workflow devicesand/or configurable according to different factors that may be relevantfor managing performance objectives.

A technically proficient support staff generally has been required tosetup and maintain device networks in which a server manages a fleet ofdevices. A technically proficient support staff also generally has beenrequired to configure devices with appropriate firmware, software,applications, and settings and to keep the various firmware, software,applications, and settings information organized and up to date. Evenwith a server-managed workflow environment, configuration informationtends to become mixed up or lost, especially when managing a largenumber of devices and/or a large number of different configurations.Furthermore, the time required to configure a standby device (e.g.,replicate a workflow device on a standby device) and then introduce thestandby device into a workflow environment is another issue which tendsto directly impact uptime or productivity, and correspondingly operatingcosts and profitability, of the workflow environment. These issues maybe magnified when support staff cannot promptly respond to a servicerequest, resulting in extended downtime.

In view of the foregoing, there further exists a need to provideimproved systems and methods for managing a fleet of devices, inparticular but without limitation, systems and methods for configuring astandby device and introducing the standby device into a workflowenvironment. The present disclosure seeks to address the foregoingshortcomings and needs, for example, by providing systems and methodsthat allow ordinary users to manage a fleet of devices without requiringmuch knowledge or skill pertaining to information technology.

Optionally, in some embodiments, the systems and methods in the presentdisclosure may be performed without requiring a server to manage thedevices in the workflow environment, thereby offsetting costs associatedwith network hardware, software, and/or support staff. Additionally,these systems and methods allow for an optimally small number of standbydevices in a workflow environment, preferably with a given standbydevice being capable of replicating multiple different workflow devices,and/or multiple workflow devices with different configurations from oneanother. The present disclosure additionally addresses theseshortcomings and needs by providing improved systems and methods forreplicating a workflow device on a standby device and methods forperforming jobs in a workflow environment.

SUMMARY

Accordingly, in one aspect, the present disclosure embraces methods ofmanaging a fleet of devices.

Managing Performance Objectives

In an exemplary embodiment, a device network is provided which includesa plurality of workflow devices. One or more of the plurality ofworkflow devices include a printer configured to produce printed mediaand/or indicia, and an inline scanner configured to obtain deviceinformation pertaining to printed media and/or indicia produced by theprinter. The device information may pertain at least in part to printedmedia and/or indicia produced by such one or more workflow devices. Forexample, the device information may include a digital image of theprinted media and/or indicia. Further, the device information maycorrespond to one or more jobs, such as jobs having been at leastpartially performed by one or more workflow devices from among theplurality.

The device information is analyzed, which for example, may includecomparing at least some device information to a parameter value. Inresponse to having detected a deviation from a parameter value, aninstruction is sent to at least one location on the device network. Thedeviation from the parameter value may correspond to printed mediaand/or indicia produced by one or more devices. The instruction triggersan action responsive to address the deviation. As examples, the actionmay include assigning one or more jobs to a different device, schedulingmaintenance for one or more workflow devices from among the plurality,and/or changing an input parameter for at least one workflow device fromamong the plurality. As an example, the input parameter may includeprint logic.

The plurality of workflow devices may include a first device, a seconddevice, and optionally an Nth device. As examples, the action mayinclude assigning one or more jobs from the first device to the seconddevice, in which case the second device would be the different device.Additionally, or in the alternative, the action may include assigningone or more jobs from the second device to the third device, in whichcase the third device would be the different device. Further, the actionmay include assigning one or more jobs from the first device to thedifferent device and scheduling maintenance for the second device.

In some embodiments, the device network may further include a standbydevice. The action may include triggering the standby device to beintroduced into a workflow environment, in which case the standby devicewould be the different device.

In some embodiments, a parameter value may be based at least in part ona quality metric corresponding to printed media and/or indicia. Thequality metric may be based at least in part on a value corresponding toor more of: print growth, print shrinkage, ink spread, edgedetermination, minimum reflectance, symbol contrast, minimum edgecontrast, modulation, printing defects, quiet zone, and decodability,cell contrast, cell modulation, fixed pattern damage, unused errorcorrection, axial non-uniformity, and grade non-uniformity.Additionally, or in the alternative, the quality metric may be based atleast in part on one or more OCR quality parameters, includingcharacter_inside_fit, character_outside_fit, character, position,background noise, and character evaluation value (CEV) grade.Additionally, or in the alternative, the parameter value may be based atleast in part on a scan parameter or a grade for such printed mediaand/or indicia, such as an overall symbol grade for indicia.Additionally, or in the alternative, a parameter value may be based atleast in part on a performance objective. Such a parameter value mayinclude a quality value, a productivity value, and/or a cost value. Aquality value may include any parameter value that has a qualitycomponent. A productivity value may include any parameter value that hasa productivity component. A cost value may include any parameter valuethat has a cost component. The performance objective (e.g., the qualityvalue, a productivity value, and/or a cost value) may be based at leastin part on the scan parameter or the grade for the printed media and/orindicia, such as the overall symbol grade for such indicia. The actionmay include changing an input parameter for at least one workflow devicein order to change the parameter value based on the performanceobjective.

In yet another exemplary embodiment, a device network includes aplurality of workflow devices, at least some of which include averification system. In some embodiments, a device may include aproduction system integrated with a verification system. Additionally,or in the alternative, a plurality of devices may include a first devicehaving a production system and a second device having a verificationsystem. The first device and the second device may be communicativelycoupled. A production system may be configured to produce outputs, and averification system may be configured to obtain device informationpertaining to outputs. Device information at least in part pertaining tooutputs produced by one or more of the workflow devices from among theplurality is compared to a parameter value, and responsive to detectinga deviation from the parameter value, an instruction is sent to at leastone location on the device network. The instruction triggers an actionresponsive to address such deviation. In some embodiments, one or moredevices may include a printer configured to produce printed media and/orindicia, and/or a scanner/verifier configured to obtain deviceinformation pertaining to the printed media and/or indicia. The scannermay be an inline scanner. The device information may include a digitalimage of the printed media and/or indicia. Device information obtainedby the verification system is compared to a parameter value, and inresponse to having detected a deviation from a parameter value, aninstruction is sent to at least one location on the device network. Theinstruction triggers an action responsive to address the deviation.

In yet another exemplary embodiment, a system for managing a fleet ofdevices is provided. The system may include a plurality of workflowdevices and a device server. At least some of the workflow devicesinclude a printer configured to produce printed media and/or indicia,and at least some of the workflow devices include a scanner configuredto obtain device information pertaining to the printed media and/orindicia. The device server is configured to: compare device informationto a parameter value, and to send an instruction to at least onelocation on the device network in response to a deviation from theparameter value having been detected. The instruction triggers an actionresponsive to address such deviation.

Introducing Standby Devices into Workflow Environments

In yet another exemplary embodiment, a device network is provided, andresiding on the network are a plurality of workflow devices, each havingbeen assigned a job in a workflow environment, and one or more standbydevices, each residing on standby to one or more of the workflowdevices. The plurality of workflow devices may each have configurationdata stored in memory thereof, and in some embodiments, theconfiguration data stored in one workflow device differs in at least onerespect from configuration data stored in at least one additionalworkflow device.

Responsive to a triggering event having occurred with respect to aworkflow device, the workflow device may cause the configuration data(e.g., a firmware file, a software file, an application file, and/orsettings information) stored in memory thereof to be sent to a standbydevice selected from among the one or more standby devices, andresponsive to receiving the configuration data, the selected standbydevice may be configured to install firmware, software, and/or anapplication in memory of the standby device and configure settings ofthe standby device according to the settings information. The standbydevice then may be introduced into the workflow environment, forexample, in substitution for the workflow device, and may beginperforming an assigned job in the workflow environment.

In some embodiments, one or more standby devices each broadcast statusinformation to at least one of the plurality of workflow devices. Thestatus information may include an identity and a location (e.g., an IPaddress), and a status indicating availability of the device (e.g., forintroducing the workflow device into the workflow environment). In someembodiments, a workflow device selects a standby device based at leastin part on status information. In some embodiments, the configurationdata sent to the standby device differs from configuration data storedin memory of at least one other workflow device from among theplurality. The triggering event may include detecting one or more of: adevice failure, scheduled downtime, a production requirement, a loss ofconnectivity in respect of another workflow device, a standby device, oranother device or resource on a device network, a deviation from aparameter value, and a user input.

In another aspect, the present disclosure embraces methods ofconfiguring a standby device for a job in a workflow environment. In anexemplary embodiment, a workflow device and a standby device areprovided, and the workflow device and the standby device are incommunication with one another, and the workflow device hasconfiguration data (e.g., a firmware file, a software file, anapplication file, and/or settings information) stored in memory thereof.Configuration data is sent from the workflow device to the standbydevice, and responsive to receiving the configuration data, the standbydevice installs the firmware, software, and/or an application in memoryof the standby device and configures settings of the standby deviceaccording to the settings information.

In another aspect, the present disclosure embraces methods of performinga job in a workflow environment. In an exemplary embodiment, a firstdevice and a second device are provided, and the first device and thesecond device are in communication with one another, and the firstdevice has configuration data (e.g., a firmware file, a software file,an application file, and/or settings information) stored in memory ofthe first device. A job is performed using the first device, and thenresponsive to a triggering event, configuration data from the firstdevice is sent to the second device. Responsive to receiving theconfiguration data, the second device installs the firmware, software,and/or an application in memory of the second device and configuressettings of the second device according to the settings information; andthen the job is further performed using the second device.

In some embodiments, a standby device broadcasts status information to aworkflow device. The status information may include an identity, alocation, and a status indicating availability of the standby device. Insome embodiments, a workflow device and a standby device reside on adevice network additionally comprising at least one additional workflowdevice. Each workflow device may have configuration data stored inmemory thereof, and the configuration data may differ in at least onerespect from the configuration data stored in memory of the at least oneadditional workflow device.

In some embodiments, configuration data sent to a standby devicecorresponds to a first job assigned to a workflow device. The first jobmay differ in at least one respect from a second job assigned to one ofthe at least one additional workflow devices. The standby device may beconfigured to perform the first job upon installing firmware in memoryof the standby device and configuring settings of the standby deviceaccording to settings information.

In some embodiments, a workflow device selects a standby device over atleast one additional standby device based at least in part on a firstjob that has been assigned to the workflow device, for example, becausethe standby device selected is configurable to perform the first job.

In some embodiments, configuration data is sent from a workflow deviceto a standby device automatically in response to a triggering event. Thetriggering event may include detecting one or more of: a device failure,scheduled downtime, a production requirement, a loss of connectivity inrespect of another workflow device, a standby device, or another deviceor resource on a device network, a deviation from a parameter value, anda user input.

In accordance with the present disclosure, a standby device may beintroduced into a workflow environment, optionally in substitution for aworkflow device. The standby device may broadcast updated statusinformation to at least one other device residing on a device network.Such updated status information may include an identity, a location, anda status indicating that the device has been removed from standby and/orintroduced into a workflow environment.

In another exemplary embodiment, configuration data (e.g., a firmwarefile, a software file, an application file, and/or settings information)is stored in memory of a first standby device selected from among one ormore standby devices, and responsive to a triggering event havingoccurred, the first standby device may be configured to identify astandby device from among the one or more standby devices, and toinstall firmware, software, and/or an application in memory of one ofthe one or more standby devices, and configure settings of such standbydevice according to the settings information. The standby deviceidentified by the first standby device may be the first standby deviceitself, or another standby device identified from a plurality of standbydevices. The identified standby device then may be introduced into theworkflow environment, for example, in substitution for a workflowdevice, and may begin performing an assigned job in the workflowenvironment.

In another exemplary embodiment, a first device and a second device areprovided, and the first device and the second device are incommunication with one another, and the first device has configurationdata e.g., a firmware file, a software file, an application file, and/orsettings information) stored in memory of the first device.Configuration data from the first device is sent to the second device. Ajob is performed using the first device, and then responsive to atriggering event, the second device installs the firmware, software,and/or an application in memory of the second device and configuressettings of the second device according to the settings information; andthen the job is further performed using the second device.

Managing Performance Objectives with Standby Devices

In yet another exemplary embodiment, a device network is provided whichincludes a plurality of workflow devices, one or more standby deviceseach residing on standby to one or more of the workflow devices, andmemory storage. The memory storage has configuration data correspondingto one or more of the workflow devices stored thereon. The configurationdata includes firmware and settings information corresponding to therespective job assigned to the one or more workflow devices. Theworkflow devices may include printers configured to produce printedmedia and/or indicia, and inline scanners configured to obtain deviceinformation pertaining to printed media and/or indicia produced by theprinter. The device information may pertain at least in part to printedmedia and/or indicia produced by such workflow devices. For example, thedevice information may include a digital image of the printed mediaand/or indicia. Further, the device information may correspond to one ormore jobs, such as jobs having been at least partially performed by oneor more workflow devices from among the plurality.

The device information is analyzed, which for example, may includecomparing at least some device information to a parameter value. Inresponse to having detected a deviation from a parameter value, aninstruction is sent to at least one location on the device network. Thedeviation from the parameter value may correspond to printed mediaand/or indicia produced by one or more devices. The instruction triggersone or more actions responsive to address the deviation. As an example,the one or more actions may include causing configuration data to besent to a standby device selected from among the one or more standbydevices.

Responsive to the standby device receiving the configuration data, thestandby device installs the respective firmware in memory of the standbydevice and configures settings of the standby device according to therespective settings information. The standby device is then introducedinto the workflow environment, for example, in substitution for one ormore workflow devices from among the plurality. One or more jobs havingbeen assigned to the one or more workflow devices are assigned to thestandby device having been introduced into the workflow environment, forexample, when the standby device is ready to perform the one or morejobs.

In some embodiments, the one or more actions may additionally includechanging an input parameter for at least one workflow device from amongthe plurality, and/or changing an input parameter for at least onestandby device from among the plurality. The input parameter may includeprint logic. Additionally, maintenance may be scheduled for at least oneworkflow devices from among the plurality and/or for at least onestandby device from among the plurality.

The plurality of workflow devices may include a first device, a seconddevice, and optionally a third device. The deviation from the parametermay correspond to printed media and/or indicia produced by the firstdevice, and the standby device may be introduced into the workflowenvironment in substitution for the second device, with the first deviceremaining in the workflow environment to perform the respective jobhaving been assigned to the first device. Additionally, maintenance maybe scheduled for the second device.

In some embodiments, the standby device is selected based at least inpart on status information having been broadcast to at least onelocation on the device network. The status information may include anidentity, a location, and a status indicating availability of thestandby device.

In some embodiments, the configuration data sent to the standby devicediffers from configuration data corresponding to at least one otherworkflow device from among the plurality. The configuration data sent tothe standby device may correspond at least in part to a first jobassigned to the workflow devices, which first job differs in at leastone respect from a second job assigned to at least one additionalworkflow device from among the plurality. A standby device may beselected from among the plurality over at least one additional standbydevice, based at least in part on the standby device being configurableto perform the first job assigned to the workflow devices.

In yet another exemplary embodiment, a workflow device and a standbydevice are provided. The workflow device may include a production systemand/or a verification system. The production system may be configured toproduce outputs, and the verification system may be configured to obtaindevice information pertaining to outputs. The production system may be aprinter configured to produce printed media and/or indicia, and theverification system may be a scanner configured to obtain deviceinformation pertaining to the printed media and/or indicia.

Responsive to a triggering event having occurred with respect to theworkflow device, configuration data is sent to the standby device. Thetriggering event may be based at least in part on a deviation from aparameter value having been detected with respect to device informationat least in part pertaining to an output produced by the productionsystem. The configuration data includes firmware and settingsinformation. As an example, the parameter value may be based at least inpart on a quality metric corresponding to at least some of the outputs,such as printed media and/or indicia, produced by the workflow device.

Responsive to the standby device receiving the configuration data, thefirmware is installed in memory of the standby device and the settingsof the standby device are configured according to the settingsinformation. Additionally, an input parameter for the workflow devicemay be changed and/or an input parameter for the standby device may bechanged. The standby device is introduced into the workflow environmentin substitution for the workflow device one or more jobs having beenassigned to the workflow devices are assigned to the standby device, forexample, when the standby device is ready to perform the one or morejobs.

The foregoing summary is illustrative only, and is not intended to be inany way limiting. In addition to the illustrative features andembodiments described above, further aspects, features, and embodimentswill become apparent by references to the drawings, the followingdetailed description, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically depicts one embodiment of a device network.

FIG. 2 schematically depicts one embodiment of a device network having aplurality of workflow environments.

FIG. 3 schematically depicts one embodiment of a device network having aplurality of workflow devices and a standby device.

FIG. 4 schematically depicts one embodiment of a device network having aplurality of workflow devices and a plurality of standby devices.

FIG. 5 schematically depicts another embodiment of a device networkhaving a plurality of workflow devices and a plurality of standbydevices.

FIG. 6 schematically depicts yet another embodiment of a device networkhaving a plurality of workflow devices and a plurality of standbydevices.

FIGS. 7A through 7F schematically depict various embodiments of one ormore devices having a production system and/or a verification.

FIG. 8A is a flow chart showing one embodiment of steps or featuresconfigured for managing a fleet of devices.

FIG. 8B schematically depicts one embodiment of a device networkconfigured for managing a fleet of devices.

FIG. 8C is a flow chart showing exemplary types of device informationwhich might be utilized when managing a fleet of devices.

FIG. 8D is a flow chart showing exemplary analytical techniques whichmight be utilized when managing a fleet of devices.

FIG. 8E is a flow chart showing one embodiment of steps or featuresconfigured for comparing one or more aspects of device information toone or more parameter values.

FIG. 8F is a flow chart showing exemplary device instructions whichmight be utilized when managing a fleet of devices.

FIG. 9 schematically depicts yet another embodiment of a device networkconfigured for managing a fleet of devices.

FIGS. 10A through 10F depict flow charts showing various exemplaryschema for managing a fleet of devices.

FIGS. 11A through 11C shows exemplary formula which may be utilized whenoptimizing for performance objectives.

FIG. 12 is a flow chart showing an exemplary embodiment of steps orfeatures configured for addressing quality assurance matters.

FIG. 13 is a flow chart showing yet another embodiment of steps orfeatures configured for managing a fleet of devices.

FIG. 14 shows an exemplary list of triggering events for introducing astandby device into a workflow environment.

FIG. 15 schematically depicts an exemplary sequence of steps or featuresfor configuring a standby device for introducing a standby device into aworkflow environment.

FIG. 16 schematically depicts a standby device having been introducedinto a workflow environment, in place of a workflow device having beenremoved from the workflow environment.

FIG. 17 shows an exploded view of one embodiment of a graphical userinterface of a standby device, indicating that the standby device isready to be introduced into a workflow environment.

FIG. 18 is a flow chart showing one embodiment of steps or featuresconfigured for managing a fleet of devices, additionally embracing oneembodiment of steps or features for configuring a standby device for ajob in a workflow environment, and one embodiment of steps or featuresfor performing a job in a workflow environment.

FIG. 19 is a flow chart showing another embodiment of steps or featuresconfigured for managing a fleet of devices, additionally embracinganother embodiment of steps or features for configuring a standby devicefor a job in a workflow environment, and another embodiment of steps orfeatures for performing a job in a workflow environment.

DETAILED DESCRIPTION

In the following detailed description, systems and methods of managing afleet of devices are described in greater detail with reference to theaccompanying figures. More particularly, but without limitation, thepresent disclosure describes systems and methods for deploying devicesin a workflow environment and assigning jobs to those devices, formanaging process parameters of devices, for introducing a standby deviceinto a workflow environment, and for performing jobs in a workflowenvironment. Such jobs may include any tasks assigned to a workflowdevice, or any functionality for which a workflow device is utilized, ina workflow environment. Numerous specific details are set forth in orderto provide a thorough understanding of the present disclosure. It willbe apparent, however, to one skilled in the art that the presentlydisclosed methods may be performed without some or all of these specificdetails. In other instances, well known aspects have not been describedin detail in order not to unnecessarily obscure the present disclosure.The following detailed description is therefore not to be taken in alimiting sense, and it is intended that other embodiments are within thescope of the present disclosure.

Exemplary Device Networks and Workflow Environments

Exemplary device networks which may be implemented for various exemplaryworkflow environments are shown in FIGS. 1-6. A device network mayinclude one or more workflow devices 100, 200, 300, 400, 500, 600. Theworkflow devices may be deployed in a workflow environment, and jobs maybe assigned to the workflow devices. In some embodiments, a devicenetwork may additionally include one or more standby devices (e.g.,FIGS. 3-6, 302, 402, 502, 602), residing on standby to one or more ofthe plurality of workflow devices. A standby device may be introducedinto a workflow environment as or when needed, and jobs also may beassigned to the standby device.

A workflow environment may include any environment where devices areused perform jobs in a workflow. For example, but without limitation,the present disclosure is particularly applicable to devices such asprinters and scanners, which may be used in environments such aswarehouses, distribution centers, or manufacturing facilities, inworkflows such as receiving, assembly, order fulfillment, and shipping.Further exemplary devices and exemplary workflow environments arediscussed below. Each workflow device may be assigned a job to performin the workflow environment, and/or each workflow device may be assignedto a user or group of users who use the assigned workflow device toperform various jobs in the workflow environment.

As shown in FIG. 1, a device network may include a first device 102, anda second device 104. The first device 102 may be a workflow device, andthe second device 104 may be a standby device or a workflow device. Asshown in FIG. 2, a device network may include a plurality of workflowenvironments. For example, the exemplary device network shown in FIG. 2includes a first workflow environment 202, a second workflow environment204, and an N-th workflow environment 206. Each workflow environment mayinclude one or more devices 208, 210, 212, which may include one or moreworkflow devices and one or more standby devices.

With reference to FIG. 3, an exemplary device network may include aplurality of workflow devices 300 and at least one standby device 302.More particularly but without limitation, the exemplary device networkof FIG. 3 includes a first workflow device 304, a second workflow device306, an Nth workflow device 308, and at least one standby device 302.For purposes of clarity, in some embodiments a device network mayalternatively include a single workflow device 102 and a single standbydevice 104.

Optionally, a device network may also include a server 106 and memorystorage 108. In some embodiments, the server may be used for managingthe fleet of devices in accordance with the present disclosure. Forexample, a server 106 may be used for acquiring device information, foranalyzing device information, and/or for sending device instructions. Insome embodiments, the server 106 may be used for managing communicationsbetween devices on a device network, for example, when managingperformance objectives as discussed below. Additionally, the server 106may be used, for example, for general networking purposes such asassigning IP addresses. However, in some embodiments the server 106 maybe omitted in accordance with the present disclosure, which offsetscosts associated with network hardware, software, and/ortechnical/skilled support staff. In various embodiments, memory storagemay be accessible via the device network (e.g., a database), and/ormemory storage may be housed within one or more of the devices (e.g., aworkflow device, a standby device) or directly connected to one or moreof the devices (e.g., external flash memory).

One or more standby devices are available in the event that a workflowdevice becomes inoperable or otherwise taken out of service. In someembodiments, a device network may include a very large number ofworkflow devices and a relatively small number of standby devices. Forexample, as shown in FIG. 4, an exemplary device network includes fifty(50) workflow devices 400 (workflow devices 4-49 omitted for clarity),and a relatively smaller plurality standby devices 402. As an additionalexample, FIG. 5 shows another exemplary device network which includestwo hundred fifty (250) workflow devices 500 (workflow devices 4-249omitted for clarity), and one or more standby devices 502. Moreparticularly, and without limitation, the workflow devices 400/500respectively shown in FIGS. 4 and 5 include a first workflow device404/504, a second workflow device 406/506, a third workflow device408/508, and a fourth workflow device 410/510.

The plurality of standby devices 402 shown in FIG. 4 includes a firststandby device 412, a second standby device 414, and a third standbydevice 416. The first standby device 412, which is shown as beingavailable for workflow devices 1-50, is designated as the primarystandby device. In some embodiments, the primary standby device will bethe first device selected from among the plurality of standby devicesfor introduction into the workflow environment. In some embodiments, theprimary standby device may be responsible for assigning, and may assign,other standby device from among the plurality of standby devices forintroduction into the workflow environment. Similarly, the one or morestandby devices 502 shown in FIG. 5 include a first standby device 512,and a second standby device 514. The first standby device 512, which isshown as being available for workflow devices 1-100, is designated asthe primary standby device for those workflow devices. Likewise, thesecond standby device 514, which is shown as being available forworkflow devices 101-250, is designated as the primary standby devicefor those workflow devices. For the reader's convenience, only a subsetof the total number and variety of devices which may reside on a devicenetwork have been visually depicted in the figures. The skilled artisanwill appreciate that the present disclosure may be implemented with awide variety of different types and number of devices (workflow devicesand/or standby devices), and the type and total number of devices may beincreased or decreased to accommodate the particular implementation.

As shown in FIGS. 3 and 4, the workflow devices are printers, such aslabel printers. As an example, such printers may be deployed in aworkflow environment such as a packaging and labeling facility or adistribution center, with each such printer having responsibility for anassigned type of printing job. This may include, for example, printingan assigned type of material, printing for a particular production line,or on-demand printing. As shown in FIG. 5, the workflow devices arehandheld scanners, such as barcode scanners or RFID scanners. As anexample, such scanners may be deployed to a group of users who use thescanners to perform various scanning jobs, such as shipping andreceiving in a parcel facility or distribution center.

As shown in FIG. 6, a device network may include a combination ofdifferent types of devices. In this exemplary device network, aplurality of workflow devices 600 are provided, which includes a firstscanner 604 and a second scanner 606, and a first printer 608 and asecond printer 610. For each of the plurality of workflow devices, thereis provided on the device network at least one standby device that isconfigurable to perform the job assigned to such workflow device, andpreferably, an optimally small number of standby devices. For example,as shown in FIG. 6, a plurality of standby devices 602 includes a firststandby device (e.g., a handheld scanner) 612 and a second standbydevice (e.g., a printer) 614. The first standby device 612 isconfigurable to perform the job assigned to the first workflow device604 and the second workflow device 606, and the second standby device614 is configurable to perform the job assigned to the third workflowdevice 608 and the fourth workflow device 610.

The exemplary device networks shown in FIGS. 1-6 are not intended to belimiting. Rather, the present disclosure may be implemented with anunlimited variety of workflow devices in an unlimited variety ofworkflow environments, and further examples are provided below. As willbe appreciated by those skilled in the art, often times, a fleet ofdevices may include different workflow devices (e.g., different featuresor functionalities) and/or multiple workflow devices with differentconfigurations (e.g., different firmware, different software, differentapplications, and/or different settings). In various embodiments of thepresent disclosure, a device network may include identical devices,common devices (e.g., not identical, but sharing some common feature,functionality, or configuration), different devices (e.g., devices thattypically would not be assigned to the same job because of somedifferent feature, functionality, or configuration), or a combination ofidentical devices, common devices, and different devices.

Such differences may arise for any number of reasons. For example, insome workflow environments there may be several different jobs, and adifferent workflow device or a different configuration may be requiredor preferred over others when performing a given job. Similarly,different users may require or prefer a different workflow device or adifferent configuration. Additionally, with respect to replacements andupgrades, it is common for only a subset of a fleet of devices to bereplaced or upgraded, resulting in a fleet of devices with variousdifferences. Likewise, when new devices are added to an existing fleet,it is common for the new devices to have differences over thepreexisting devices. Accordingly, it can be expected that the number ofdifferences among various devices in a fleet increase as the size of thefleet increases. Yet, it is an object of the present disclosure toprovide an optimally small number of standby devices to accommodateworkflow device failures and downtime for even a very large fleet ofdevices, and even when the fleet of devices includes several variousdifferent devices and/or different configurations.

In accordance with the present disclosure, various devices on a devicenetwork communicate with one another, for example, so that a standbydevice can be introduced into a workflow environment when needed. Anycommunication protocol may be used, such as TCP/IP. A server 106, suchas a DHCP server, may provide IP addresses to the various devices on thedevice network. A device network may be configured as a LAN, a WAN, orany other network configuration. In some embodiments, a device networkmay utilize wireless network or a Bluetooth technology. In someembodiments, network management software may be utilized.

Each device may communicate with any other device, as desired by theskilled artisan. In some embodiments, a standby device communicates toat least one workflow device, and additionally or alternatively, aworkflow device communicates to at least one standby device.

In some embodiments, a device network may include different devices, anddevices on the network may communicate either only with other deviceswith some commonality (e.g., common feature, common functionalities,common models, common configuration), or devices on the network maycommunicate both to common devices and different devices. Accordingly,such communications may be broadcast, multicast, unicast, or any otherdesired routing scheme.

For example, in the device network shown in FIG. 3, the at least onestandby device 302 may communicate with each of the plurality ofworkflow devices 300. Additionally, or in the alternative, each of theplurality of workflow devices 300 may communicate with the at least onestandby device 302, and/or to one another. More particularly, andwithout limitation, the first workflow device 304 may communicate with astandby device 302, and/or to the second workflow device 306 and the Nthworkflow device 308.

As another example, workflow devices and standby devices may beconfigured to communicate only to other compatible devices. For example,with reference to FIG. 4, the first standby device 412 shows as beingavailable for workflow devices 1-50 (and is shown as being the primarystandby device), the second standby device 414 shows as being availablefor workflow devices 1-25, and the third standby device 416 shows asbeing available for workflow devices 26-50. Such availability may bebased on configurability of the devices, prioritization of the standbydevices allocation to workflow devices, or other criteria that may beselected by the skilled artisan. Accordingly, in some embodiments thefirst workflow device 404 may be configured to communicate with thefirst standby device 412 (i.e., the primary standby device), but not thesecond standby device 414 or the third standby device 416; whereas thefirst standby device 412 may be configured to communicate with all ofthe workflow devices 400, as being the primary standby device to all ofthem. Similarly, the second workflow device 406 may be configured tocommunicate with the second standby device 414 and to the third standbydevice 416, while the second standby device 414 may be configured tocommunicate with the second workflow device 406 and to the thirdworkflow device 408. Likewise, the fourth workflow device 410 and thethird standby device 416 may be configured to communicate with oneanother.

In some embodiments, a device sends communications comprising statusinformation to one or more other devices on the device network, forexample, to allow the one or more other devices to ascertain the statusof the device sending the communications. Status information may includean identity, a location, and a status for the device. As examples, acommunication sent by a workflow device may include, for example,information that would allow other devices on the device network toascertain that the workflow device is residing on the device network,the identity and location of the workflow device, a job and/or userassigned to the workflow device, whether or not the workflow device isfunctioning properly, and/or the compatibility requirements of thedevice. Communications sent by a standby device may include, forexample, information that would allow other devices on the devicenetwork to ascertain that the standby device is residing on the network,the identity and location of the standby device, the status of thedevice, whether the device is available for replicating, and/or thecompatibility of the standby device to be configured for various jobsand/or users in the workflow environment.

As illustrated by these examples, some device networks may include avery large number of workflow devices, such ten or more, fifty or more,one hundred or more, or even one thousand or more workflow devices. Evenwhen a device network has a very large number of workflow devices,methods of managing a fleet of devices in accordance with the presentdisclosure allow for an optimally small number of standby devices. Assuch, the present disclosure advantageously reduces the cost ofproviding and maintaining standby devices for a workflow environment,for example, because fewer standby devices are necessary to accommodatethe standby requirements of the workflow environment. The methodsprovided by the present disclosure can be especially advantageous forhigh-volume workflow environments.

The skilled artisan can select the optimal number of standby devices,for example, based on the number of workflow devices deployed in aworkflow environment and the likelihood that any one or more of thosedevices may experience downtime. When selecting the optimal number ofstandby devices, the skilled artisan may also consider maintenancerequirements and service intervals for various devices, as well as theextent to which a given standby device would be configurable to performthe various jobs to which the workflow devices are assigned, or toaccommodate requirements of the various users. In some workflowenvironments, it may be desirable for every single workflow device tohave a corresponding standby device. Such a 1:1 ratio may be appropriatein workflow environments where downtime is extremely expensive or hassevere consequences. However, in most workflow environments, the skilledartisan will prefer to provide only a few standby devices to accommodatea very large number of workflow devices and/or users. Exemplary ratiosfor the number of workflow devices per compatible standby deviceinclude, without limitation from 1:1 to 1000:1 or greater, for example,10:1, 20:1, 50:1, 100:1, 1000:1 or greater.

Managing Performance Objectives

Various embodiments of the present disclosure embrace systems andmethods for managing performance objectives for a device or a fleet ofdevices, including systems and methods for managing output quality,productivity or uptime, and/or cost-efficiency. In general, the systemsand methods disclosed herein embrace obtaining information directly orindirectly from one or more devices among a fleet, and utilizing suchinformation manage a fleet of devices or individual devices from amongthe fleet. The fleet of devices may include multiple different workflowenvironments, or a subset of devices within a workflow environment.Information obtained from a device or fleet of devices may be used tomanage that same device or fleet, and/or such information may be used tomanage a different device or a different fleet of devices other thanthat from which the information was obtained. Similarly, the informationobtained from devices deployed in one workflow environment may be usedto manage devices in that same workflow environment, and/or suchinformation may be used to manage one or more different workflowenvironments. Moreover, information obtained from one enterprise may beutilized to manage devices or workflow environments within thatenterprise, and/or such information may be used to manage one or moredifferent enterprises.

Exemplary Devices

In some embodiments, the systems and methods disclosed herein utilizedevices having a production system and/or a verification system. Such aproduction system may be configured to produce outputs, and such averification system may be configured to verify outputs. In variousembodiments, frequent verifications may be obtained, up to and includingverifying every output. Alternatively, frequent verifications may beobtained for only a subset of outputs, including verifying every N-thoutput produced by a device as may be appropriate for the particularsetting, such as every 2^(nd) output, every 3^(rd) output, every 4^(th)output, every 10^(th) output, every 100^(th) output, every 1,000^(th)output, or even further between verifications when appropriate. Whenverifying only a subset of outputs, the skilled artisan may select afrequency of verification by balancing the probability of a meaningfuldeviation from an output parameter (e.g., a statistically significantdeviation, a deviation constituting a failed output, etc.) as betweenN-number of outputs against the cost of verifying outputs morefrequently and the consequences in the event that such deviation betweenN-number of outputs goes undetected. In some embodiments, providing aproduction system integrated with or communicatively coupled with averification system may make verifying every output a feasible option,particularly in settings where independent verification of every outputwould be impractical. Accordingly, exemplary devices utilize averification system (e.g., a verification system integrated with orcommunicatively coupled with a production system) to acquire deviceinformation including information pertaining to outputs and/orinformation pertaining to verifications, which device information maythen be utilized in the systems and methods for managing fleets ofdevices disclosed herein, including, without limitation, systems andmethods for managing performance objectives, systems and methods formanaging maintenance and service requirements, systems and methods formanaging the selection of devices device configurations, and/or systemsand methods for deploying or introducing devices into workflowenvironments.

In one embodiment, an exemplary device may be a single device havingboth a production system and a verification system. In anotherembodiment, an exemplary device comprising a production system may becommunicatively coupled to another exemplary device comprising averification system. For example, FIG. 7A shows a schematic depictingone embodiment of an exemplary device 700 having a production systemintegrated with a verification system. As shown, a production system 702produces outputs 704, and a verification system 706 verifies the outputs704 produced by the production system 702, providing verified outputs708. A processor 710 communicatively couples the production system 702and the verification system 706. The exemplary device 700 may be incommunication with a server 106 (for example to manage communicationsbetween the exemplary device 700 and other devices on a device network),and memory storage 108 may be provided (for example to store deviceinformation). Another exemplary embodiment having a production systemintegrated with a verification system is shown in FIG. 7B. As shown, afirst device 700 includes a production system 702, and a second device712 includes a verification system 706, and the production system 702and the verification system 706 are communicatively coupled. Similarly,in the exemplary embodiment shown in FIG. 7B, the production system 702produces outputs 704, and the verification system 706 verifies theoutputs 704 produced by the production system 702, providing verifiedoutputs 708. The first device 700 and the second device 712 arecommunicatively coupled, for example, by a first processor 710 and asecond processor 714. Both the first device 700 and the second device712 may be in communication with the server 106 (for example to managecommunications between the exemplary device 700 and other devices on adevice network), and memory storage 108 may be provided (for examplestore device information).

Various embodiments may utilize any device that might be contemplated bythe skilled artisan. For example, but without limitation, devices whichmay be of particular interest include devices having printing or markingassemblies, scanner/verifier assemblies, and combinations thereof. Asexamples, FIGS. 7C through 7F show exemplary embodiments of deviceshaving a printing assembly and/or a scanner/verifier assembly which maybe utilized in accordance with the present disclosure. It is to beunderstood, however, that other exemplary devices are disclosed hereinwhich also may be utilized in various embodiments, and the skilledartisan will appreciate that even further, additional devices are withinthe spirit and scope of the present disclosure.

In one embodiment, an exemplary device 700 may include a productionsystem 702 (e.g., a printing assembly) and a verification system 706(e.g., a scanner/verifier assembly) integrated into a single device,such as a printer having an inline scanner/verifier or an “all-in-one”printer/scanner device (e.g. FIG. 7A, 7C). In another embodiment, aproduction system 702 (e.g., a printing assembly) and a verificationsystem 706 (e.g., a scanner/verifier assembly) may be provided asseparate devices. For example, a first device 700 may include a printingassembly, and a second device 712 may include a scanner/verifierassembly (e.g., FIGS. 7B, 7C, 7D through 7F). The separate devices maybe communicatively coupled, providing a production system 702 (e.g., aprinting assembly) integrated with and a verification system 706 (e.g.,a scanner/verifier assembly). In various embodiments, a productionsystem 702 may include a printing assembly. The production system 702provides outputs 704. The outputs may include printed media and/orindicia having been printed on such printed media. A verification system706 may include a scanner/verifier assembly, and the verified outputsmay include printed media and/or indicia having been verified by thescanner/verifier assembly; and/or scanned images, glyphs, indicia, orother material having been printed on such verified printed media. Insome embodiments, the production system may include a scanner/verifierassembly, and the outputs and/or verified outputs may include printedmedia and/or indicia having been verified by the scanner/verifierassembly; and/or scanned images, glyphs, indicia, or other items havingbeen printed on such verified printed media. In various other exemplarydevices, an output may include any product or result produced by orobtained from a device or production system, and a verification systemmay include any system or device configured to measure or verify acharacteristic or feature of such output, producing verified outputs.Verified outputs may include any product or result produced by orobtained from a device or production system that has been verified by averification system.

As shown in FIG. 7C, an exemplary system or device 700 is provided,which in some embodiments includes a production system integrated with averification system. In an exemplary embodiment, the system or device700 includes integrated within a single device, both a production system716, which in an exemplary embodiment includes a printing assembly, anda verification system 718, which in an exemplary embodiment includes anin-line scanner/verifier assembly. Alternatively, in some embodiments,the production system 716 and the verification system 718 shown in FIG.7C may be provided as separate devices. For example, FIG. 7C alsoencompasses embodiments in which a printing assembly and ascanner/verifier assembly are provided as stand-alone or separatedevices, such as respectively shown in FIG. 7D (printingassembly/production system 716) and FIG. 7E (scanner/verifierassembly/verification system 718). Further, in another embodiment asshown in FIG. 7F, a production system 716 and a verification system 718may be provided as stand-alone or separate devices, yet communicativelycoupled with one another, for example providing a printingassembly/production system 716 integrated with a scanner/verifierassembly/verification system 718.

As shown in FIG. 7C, an exemplary system or device 700 may comprise athermal transfer printer. Alternatively, any other printing or markingdevices may be utilized in accordance with the present disclosure, andfurther examples are provided herein. Printing assemblies such as theexemplary thermal transfer printer shown in FIG. 7C are well known inthe art, and thus will be discussed only in brief detail. As shown inFIG. 7C, a drive assembly 724 includes a stepper motor 726 and a platenroller 728. The stepper motor 726 advances the platen roller 728 indiscrete increments, which, in turn, advances printable medium 730between the platen roller 728 and one or more print heads 732 in aprinting direction shown by an arrow 734. The position of the printablemedium 730 may be tracked with a processor 710 associated with a counterwhich maintains a count of the steps taken by the stepper motor 726.Alternatively, a tachometer or other conventional device (not shown) maybe used to track the position of the printable medium either directly,or indirectly.

The one or more print heads 732 are activated by a print driver 736. Theprint driver 736 is driven by print commands which are generated byprint logic. The print commands comprise retrieved print data incombination with a system clock signal or strobe signal under control ofthe printer processor 700 to ensure proper timing and spacing ofsuccessive sequential parts of the images, glyphs, indicia, or otheritems to be printed or marked by the one or more print heads 732. Theone or more print heads 732 have an array of print elements 738, and areoperable for printing or marking a plurality of sequential parts of suchimages, glyphs, indicia, or other items onto a corresponding pluralityof sequential segments of the printable medium 730, producing printedmedia 740.

The print driver 736 uses the print commands generated by the printlogic to provide energizing signals to the array of print elements 730of the print head 732. The energizing signals activate the printelements 730, which when activated are effective to place a mark on therespective sequential segment of the printable medium 730. In thethermal transfer printer of the embodiment shown in FIG. 7C, when anindividual print element 738 is energized, heat is generated, and suchheat is transferred to an adjacent region of thermally sensitive printribbon 742. The print ribbon 742 contains ink, which when melted by heattransferred from one or more printer elements 738 releases from theprint ribbon 742 and transfers to the printable medium 730, therebyapplying a mark on the respective sequential segment of the printablemedium 730. Alternatively, a thermally sensitive printing medium may beused, as is conventional for thermal printers. In that case, theprintable medium 730 may comprise a web of thermally sensitive materialsuch as heat-sensitive paper or plastic. While the print head 732 shownin FIG. 7C is a thermal print head, other print heads may be used, suchas in laser printers, ink drop printers, dot-peen printers, and furtherexamples as disclosed herein. The operation of print heads isconventional and well-known and, for the sake of brevity and clarity,will not be described in further detail.

Further referring to FIG. 7C, printed media 740 advances past ascanner/verifier assembly 718, which comprises an image head or scanner744. The image head 744 is configured to capture information about theimages, glyphs, indicia, or other items or sequential parts thereofproduced by the printing or marking assembly 716. The image head 744optically images, digitizes, or samples at least a portion of suchimages, glyphs, indicia, or other items printed by the print head 732.In an exemplary embodiment, the scanner/verifier assembly 718 takesadvantage of the motion of the printed media 740 past the image head 744to successively capture each portion of printed images, glyphs, indicia,or other items as the printed images, glyphs, indicia, or other itemsadvances past the image head. The image head 744 contains an array ofphotosensitive elements, such as in a charged coupled device (“CCD”)having, for example, linear active surface pixel elements. In the caseof a CCD, several imaging samples may be taken as the printed media 740advances past the image head 744. Several imaging samples of printedmedia and/or indicia may be aggregate to provide a digitizedrepresentation or image of an entire printed media and/or indicia. Thedigitized image and/or imaging samples may be stored in memory storage108 for further processing or analysis in accordance with the presentdisclosure. Other known image heads may also be used, includingvidicons, two-dimensional semiconductor arrays, and two-dimensional CCDarrays. Operation of such a CCD image head is described in furtherdetail in U.S. Pat. No. 6,042,279, the entirety of which is herebyincorporated by reference into the present disclosure.

In some embodiments, the printing assembly 716 may include a recorder748, operable for recording the rate sensed at which the drive assembly724 imparts motive force to the printable medium 730. In someembodiments, the scanner/verifier assembly 718 may include a controller750, operable for setting a rate at which the image head 744 evaluates(optically images, digitizes, or samples) the printed media and/orindicia or sequential parts thereof. In an exemplary embodiment, a datalink may be provided, operable for communicatively coupling the printingassembly 716 and the scanner/verifier assembly 718. For example, theprinting assembly 716 may provide the scanner/verifier assembly withdata from the recorder 748 (e.g., data relating to the rate sensed atwhich the drive assembly imparts motive force to the printable medium),and the scanner/verifier assembly 718 may carry out operationsresponsive to receiving data from the printing assembly (e.g., setting arate at which the image head evaluates the printed media and/or indiciaor sequential parts thereof).

While the exemplary embodiments in FIGS. 7C through 7F discuss printingassemblies and scanner/verifier assemblies, the skilled artisan willappreciate that the spirit and scope of the present disclosure embracesnumerous other embodiments of production systems and/or verificationsystems. For example, in some embodiments a production system 702 mayinclude an instrument, and a verification system 706 may include acalibration device for calibrating the instrument; the outputs 704 maybe instrument readings, and the verified outputs 708 may be verifiedinstrument readings. Exemplary instruments include electronic scales andflow meters. As an additional example, in some embodiments a productionsystem 702 may include a dimensioner (e.g., a weighing and volumemeasuring system for measuring three-dimensional objects such aspackages, parcels, pallets, cartons, and boxes), and a verificationsystem 706 may include a scale or a calibration device for calibratingthe dimensioner; the outputs 704 may be measurements obtained from thedimensioner, and the verified outputs 708 may be verified measurements.Such other production systems and/or verification systems may includeany device or combination of devices that may be within thecontemplation of the skilled artisan, many of which other devices aredisclosed herein, and all of which are within the spirit and scope ofthe present disclosure.

Exemplary Device Networks

With reference to FIG. 8A, various embodiments of the systems andmethods for managing a fleet of devices 800 (e.g., systems and methodsfor managing performance objectives) may include any one or more stepsor features configured for: acquiring device information 802, analyzingdevice information 804, and sending device instructions based on deviceinformation 806. Device networks may be configured to provide aplurality of devices, any one or more of which may be utilized insystems and methods disclosed herein. For example, FIG. 8B shows anexemplary device network (e.g., the exemplary device network of FIG. 2),which may include features configured for receiving device information802, analyzing device information 804, and sending device instructions806. Device information may be acquired from any one or more devices,and optionally stored in memory storage 108 (e.g., FIGS. 1-9). Suchdevice information may be subjected to analysis using any one or moreanalytical techniques, and device information may be sent to one or moredevices or other locations on a device network based, at least in part,on such device information.

An exemplary device network may include one or more workflowenvironments, such as a first workflow environment 202, a secondworkflow environment 204, and an N-th workflow environment 206. Eachsuch workflow environment may include one or more devices, such as afirst plurality of devices 208, a second plurality of devices 210, and athird plurality of devices 212. A device network may be configured toacquire device information 802 from any one or more of such devices. Forexample, exemplary systems and methods may be configured for acquiringdevice information 802 including any one or more of: informationpertaining to an individual device 808; information pertaining to aworkflow environment 810, which may include information pertaining toone or more individual devices 808; and/or information pertaining to adevice enterprise 812, which may include information pertaining to oneor more workflow environments 810 and/or information pertaining to oneor more individual devices 808. A server 106 may be provided, forexample, to manage communications between devices on the device network.Memory storage 108 may be provided, for example, to store deviceinformation.

Device information may be analyzed with respect to an individual device,a workflow environment (which may include aggregated information frommultiple devices), or a whole enterprise (which may include aggregatedinformation from multiple workflow environments and/or from multipledevices). For example, exemplary systems and methods may be configuredfor analyzing device information 804 including any one or more of:analyzing information pertaining to an individual device 814; analyzinginformation pertaining to a workflow environment 816, which may includeanalyzing information pertaining to one or more individual devices 814;and/or analyzing information pertaining to a device enterprise 818,which may include analyzing information pertaining to one or moreworkflow environments and/or analyzing information pertaining to one ormore individual devices 814.

Device instructions may be sent to one or more locations on a devicenetwork, including one or more devices or other locations such as aserver 106 or memory storage 108. For example, exemplary systems andmethods may be configured for sending device instructions 806, which mayinclude any one or more of: sending instructions pertaining to anindividual device 820; sending instructions pertaining to a workflowenvironment 822, which may include sending instructions pertaining toone or more individual devices 820; and/or sending instructionspertaining to a device enterprise 824, which may include sendinginstructions pertaining to one or more workflow environments 822 and/orsending instructions pertaining to one or more individual devices 820.

Acquiring Device Information

Device information may be acquired directly from any one or moredevices, or indirectly from other locations on a device network such asa server 106 or memory storage 108. Any such device information orcombinations thereof may be utilized in accordance with the presentdisclosure. With reference to FIG. 8C, a flow chart is shown, depictingexemplary types of device information which might be acquired 802 invarious embodiments. For example, exemplary systems and methods may beconfigured for acquiring device information pertaining to any one ormore of: identities or locations of devices 830, process parameters 831,outputs of devices 832, verifications/quality measurements 833,performance objectives (e.g., quality, productivity, cost) 834,environmental parameters 835, components and/or consumables utilized bydevices 836, device configurations or settings 837, jobs assigned todevices 838, and users assigned to devices 839. Aspects of such deviceinformation may be relationally associated to one another, for examplein a database housed in memory storage 108.

Information pertaining to components and/or consumables may include, forexample, information about print heads, drums, rollers, toner, ink,printing ribbon, printable medium, and any other replaceable parts orconsumable items. Such information may include a consumption rate, acount or estimate of a supply/level/useful life remaining, an alarm forlow-supply/low-level/low-useful-life alarms, a maintenance or servicerequirement with respect to a component and/or consumable, and the like.

In an exemplary embodiment, a device comprising a production system 702produces outputs, and device information is acquired includinginformation about the production system and/or the outputs 704 havingbeen produced. Further, a device comprising a verification system 706verifies outputs, and device information is acquired includinginformation about the verification system and/or information about theverified outputs 708. Such exemplary embodiment may comprise aproduction system integrated with or communicatively coupled with averification system.

When a device, production system, or verification system comprises aprinting assembly, device information may include information aboutprinted media produced by the printing assembly, such as informationabout printed media and/or indicia having been printed thereon.

When a device, production system, or verification system comprises ascanner/verifier assembly, device information may include informationabout scans having been obtained by the scanner/verifier assembly, suchas information about printed media and/or indicia having been printed bya printing assembly. Information about scans may include a digital imageof printed media and/or indicia obtained by the scanner/verifierassembly.

A device for purposes of the present disclosure may include any deviceor combination of devices that may be within the contemplation of theskilled artisan, many of which are disclosed herein, and all of whichare within the spirit and scope of the present disclosure. In someembodiments, a device includes a thermal transfer printer, and deviceinformation includes information about a printing ribbon supply and/orinformation about a printable medium supply, such as low supply, orsimilar information about other consumables or components. In someembodiments, a device includes a laser toner printer, and deviceinformation includes information about a toner supply and/or informationabout a printable medium supply, such as low supply, or similarinformation about other consumables or components. In some embodiments,a device includes an ink drop printer, and device information includesinformation about an ink supply and/or information about a printablemedium supply, such as low supply, or similar information about otherconsumables or components. In some embodiments, a device includes apoint-of-sale device (e.g., a cash register, a payment console, etc.),and device information includes information about an ink supply and/orinformation about a printable medium supply, such as low supply, orsimilar information about other consumables or components.

In some embodiments, a printer sequentially produces a plurality ofindicia or other items and a scanner obtains a digital image of each andevery indicia or other item from among the plurality. Alternatively, ascanner may obtain a digital image of a subset of the indicia or otheritems from among the plurality. For example, a scanner may obtain adigital image of every N-th indicia or other item produced by theprinter, such as every 2^(nd) indicia or other item, every 3^(rd)indicia or other item, every 4^(th) indicia or other item, every 10^(th)indicia or other item, every 100^(th) indicia or other item. In someembodiments, a scanner may obtain one or more digital images of printedmedia and/or indicia produced by the printer when a change occurs withrespect to other device information, and thereby obtaining a collectionof device information associated with such change having occurred. Suchchange may include a change or changes pertaining to one or more processparameters, outputs, quality, productivity, environmental parameters,consumables, settings, jobs, and/or users.

In some embodiments, a triggering event as discussed below may be basedat least in part on an aspect of device information.

In some embodiments, acquiring device information may include generatingfurther device information 840. Such further device information mayinclude outputs from data management activities, such as: extracting asubset of data from device information, e.g., for further processing orstorage; cleaning device information, e.g., to remove corrupt orinaccurate data; annotating device information, e.g., with comments,explanations, or to provide context; integrating device information,e.g., to combine device information from multiple sources such ascombining device information from multiple devices, multiple workflowenvironments, multiple device networks, multiple enterprises, and/orcombining device information with different data such as data frombusiness intelligence systems, enterprise resource management systems,and the like; and/or providing data visualizations or other datarepresentations, for example to present data in a readable,aesthetically pleasing, or otherwise user-friendly format. Furthermore,any such device information may be relationally associated with otherdevice information, for example, for further processing in accordancewith the present disclosure.

Analyzing Device Information

Any one or more aspects of device information may be analyzed usinganalytical techniques known in the art. Any such analytical technique orcombinations thereof may be utilized in accordance with the presentdisclosure. With reference to FIG. 8D, a flow chart is shown, depictingexemplary analytical techniques which might be used to analyze deviceinformation 804 in various embodiments. For example, exemplary systemsand methods may be configured for analyzing device information (i.e.,any one or more aspects thereof) utilizing any one or more of thefollowing analytical techniques: association rule learning 850,classification tree analysis 851, genetic algorithms 852, machinelearning 853, regression analysis 854, identification ofoutliers/unusual data segments 855, data interpretation 856, datamodeling 857, predictive analytics 858, and preventative strategies 859.In some embodiments, analyzing device information may include generatingfurther device information 860, for example, information resulting fromor based on any of the foregoing analytical techniques having beenperformed on device information and/or data from other sources.

In some embodiments, one or more aspects of device information may becompared to one or more parameter values. With reference to FIG. 8E, aflow chart is shown, depicting an exemplary comparison of one or moreaspects of device information to one or more parameter values. As shown,a first aspect of device information 870 is compared to a firstparameter value 872. When a deviation from the first parameter value hasbeen detected 872, a first instruction 874 is sent, based on thedeviation from the first parameter value having been detected. The firstinstruction may be sent to at least one location on the device network.Additionally, or in the alternative, a second aspect of deviceinformation 870 can be compared to a second parameter value 876. When adeviation from the second parameter value has been detected 876, asecond instruction is sent, based on the deviation from the secondparameter value. The second instruction can be sent to at least onelocation on the device network. In addition, or alternatively, the firstaspect of device information 870 may be compared to the second parametervalue 876. Comparison of the first aspect of device information 870 tothe second parameter value 876 may occur separately from comparison ofthe first aspect of device information to the first parameter value 872,and/or following comparison of the first aspect of device information tothe first parameter value. For example, the first aspect of deviceinformation may be compared to the second parameter value 876 when adeviation from the first parameter value has not been detected 880.Alternatively, the first aspect of device information may be compared tothe second parameter value 876 when a deviation from the first parametervalue has been detected 880, such as to ascertain whether a deviationfrom both the first parameter value and the second parameter value.

As examples, the first parameter value 872 and/or the second parametervalue 876 may each include a value corresponding to one or more of: aprocess parameter, an output, a measurement or verification of anoutput, a performance objective, an environmental parameter, a componentor consumable, a setting, a job, or a user, or combinations these.Additionally, or in the alternative, a parameter value may correspond toan output from any one or more analytical techniques.

In an exemplary embodiment, device information comprising informationabout indicia having been produced by a printing assembly and/orinformation about scans having been obtained by a scanner/verifierassembly is provided. The information about scans may include a digitalimage of printed media and/or indicia obtained by the scanner/verifierassembly. One or more aspects of such device information are compared toone or more parameter values, which may include parameter values basedon verifications and/or quality measurements for printed media and/orindicia, and/or performance objectives for producing printed mediaand/or indicia. For example, such parameters may pertain to physicalcharacteristics of printed media and/or indicia or corresponding qualitymetrics (such as observed from analyzing a digital image of such printedmedia and/or indicia). The quality metric may be based on standards,including ANSI/ISO standards pertaining to printed media and/or indicia.Such standards may include one or more of: an ANSI/ISO standard gradingstructure (e.g., ISO/IEC 15415, 15416, 30116, or 29158), AIM(Association for Automatic Identification and Mobility) Direct Part Mark(DPM) Quality Guideline DPM-1-2006, USPS Merlin standards, and/orcustomized or user-defined standards. The device information may includeone or more values (e.g., measured or calculated values) attributable toone or more of such physical characteristics or corresponding qualitymeasurements for printed media and/or indicia, and the one or moreparameter values may include process control parameter values, such asspecification targets, control limits, and the like, for such physicalcharacteristics or corresponding quality measurements.

In some embodiments, for example when using an ANSI/ISO standard gradingstructure, the physical characteristics of printed media and/or indiciawhich may be evaluated include print growth, print shrinkage, inkspread, edge determination, minimum reflectance, symbol contrast,minimum edge contrast, modulation, printing defects, quiet zone, anddecodability. These characteristics are well known in the art, and aredescribed in the ANSI/ISO guidelines.

Additionally, or in the alternative, for example, when using DPM QualityGuideline DPM-1-2006, the physical characteristics of printed mediaand/or indicia which may be evaluated include decodability, cellcontrast, cell modulation, fixed pattern damage, unused errorcorrection, axial non-uniformity, minimum reflectance, and gradenon-uniformity. These characteristics are well known in the art, and aredescribed in the DPM Quality Guideline.

Additionally, or in the alternative, the physical characteristics ofprinted media and/or indicia which may be evaluated include OCR qualityparameters, including character_inside_fit, character_outside_fit,character, position, background noise, and character evaluation value(CEV) grade.

In some embodiments, device information may include one or more values(e.g., measured or calculated values) attributable to the scan parameteror grade for the printed media (e.g., as determined by an ANSI/ISOstandard or other grading structure), and the one or more parametervalues may include process control parameter values, such asspecification targets, control limits, and the like for such scanparameter or grade. In some embodiments, device information may includeone or more values (e.g., measured or calculated values) attributable tothe scan parameter or overall symbol grade for indicia (e.g., asdetermined by an ANSI/ISO standard or other grading structure), and theone or more parameter values may include process control parametervalues, such as specification targets, control limits, and the like forsuch scan parameter or symbol grade.

In some embodiments, device information may include information aboutperformance objectives for producing outputs, such as a quality value, aproductivity value, and/or a cost value, and the one or more parametervalues may include process control parameter values, such asspecification targets, control limits, and the like for such performanceobjectives.

In some embodiments, device information may include status informationfor one or more devices, such as whether the device or various systemsor components thereof are showing as operational, or whether the deviceor any such systems or components has presented an error message, or hasexperienced a failure, or a loss of connectivity in respect of anotherworkflow device, a standby device, or another device or resource on adevice network. Analyzing device information may include ascertainingany one or more aspects of such status information. For example, aparameter value may be configured to correspond to one or more aspectsof status information, and a deviation from the parameter value wouldexist when the device status does not correspond to the parameter value.

In some embodiments, analyzing device information may includeascertaining the occurrence of a triggering event. Such triggeringevents are discussed in more detail below. One example of a triggeringevent is a device failure. In an exemplary embodiment, a triggeringevent may give rise to a deviation from a parameter value. For example,a parameter value may be configured to the absence of a triggeringevent, and a deviation from the parameter value would exist upon theoccurrence of a triggering event. Alternatively, in another exemplaryembodiment, a deviation from a parameter value may give rise to atriggering event.

Sending Device Instructions

In accordance with the present disclosure, any one or more deviceinstructions may be sent to any one or more locations on a devicenetwork. Such instructions may be sent to a location associated with adevice, such as a processor or memory storage. For example, deviceinstructions may be sent to a processor 710/714, a server 106, and/ormemory storage 108. In an exemplary embodiment, device instructions maybe sent in response to a deviation from a parameter value having beendetected.

With reference to FIG. 8F, a flow chart is shown, depicting exemplarydevice instructions. For example, exemplary systems and methods may beconfigured for sending device instructions 806 (and/or for receivingdevice instructions), including instructions directed towards any one ormore of the following operations: developing a fleet configuration 870,assigning a useful life for one or more devices 871, generating amaintenance or service schedule for one or more devices 872, assigningone or more jobs to one or more devices and/or one or more users 873,selecting components/consumables 874, changing one or more inputparameters 875, scheduling maintenance or service for one or moredevices 876, requesting a standby device 877, re-routing job(s) orotherwise assigning job(s) to different devices and/or users 878, andstopping jobs 879. In some embodiments, sending device instructions mayinclude generating further device information 880, for example, deviceinformation pertaining to device instructions having been sent to one ormore devices.

In some embodiments, device instructions may be directed towardsdeveloping a fleet configuration 870. Such fleet configuration mayinclude a selection of devices to be introduced into a workflowenvironment, for example to perform one or more jobs and/or for use byone or more users. The fleet configuration may be provided for anenterprise, a workflow environment, and/or for one or more jobs or oneor more users or groups of users, such as a subset of jobs or userswithin an enterprise or a workflow environment.

In some embodiments, device instructions may be directed towardsassigning a useful life for one or more devices 871, and/or amaintenance or service schedule for one or more devices 872. Forexample, a useful life may be assigned and/or a maintenance schedule maybe generated based on an analysis of device information pertaining tothe performance of one or more devices. Such device information mayinclude information about utilization or uptime or expected utilizationor uptime of one or more devices, information about maintenancerequirements, schedules, or expected schedules, information aboutfailure rates or expected failure rates, and/or information about deviceperformance or expected performance relative to performance objectives.

In some embodiments, device instructions may be directed towardsassigning one or more jobs to one or more devices and/or one or moreusers 873. For example, jobs may be assigned to devices or users basedon information about the availability, utilization, capabilities, and/orperformance of one or more devices with respect to which jobs might beassigned. Such assignments may include nascent assignments and/orchanges to assignments for jobs having been assigned.

In some embodiments, device instructions may be directed towardsselecting components and/or consumables 874. For example, componentsand/or consumables may be selected based on information about theavailability, utilization, capabilities, and/or performance of suchcomponents and/or consumables, and/or of one or more devices whenutilizing such components and/or consumables. Such device instructionsmay include, for example, initiating orders or order schedules, orchanging orders or order schedules; and/or selecting or changingcomponents or consumables for use with one or more devices. Forprinters, components and/or consumables includes print heads, drums,rollers, toner, ink, printing ribbon, printable medium, and any otherreplaceable parts or consumable items.

In some embodiments, device instructions may be directed towardschanging one or more input parameters 875. Such input parameters mayinclude, for example, set points, manipulated variables, tuningalgorithms, controller logic, and other process control parameters.Device instructions for changing input parameters may be directedtowards one or more devices. For example, input parameters may bechanged to adjust the operation or performance of an individual device,or to adjust the operation of a plurality of devices simultaneously. Inaddition, or in the alternative, input parameters may be changed toadjust an interaction as between two or more devices.

For devices that include a printing assembly, input parameters that maybe changed in accordance with the present disclosure include: devicesettings or configurations; print logic, or print commands generated bythe print logic, such as strobe rate, timing, heat, temperature, orenergy level for printing elements; drive system parameters, such asstep rate or timing for a stepper motor; and parameters pertaining toperformance objectives.

For devices that include a scanner/verifier assembly, input parametersthat may be changed in accordance with the present disclosure include:scan rate, symbology, grading standard, and parameters pertaining toperformance objectives.

In some embodiments, device instructions may be directed towardsscheduling maintenance or service for one or more devices 876,requesting a standby device and/or configuring a standby device 877,re-routing job(s) or otherwise assigning job(s) to different devicesand/or users 878, and/or stopping jobs 789. Scheduling maintenance orservice may include scheduling based on ascertaining that a devicepresently requires maintenance or service, or predicting that a devicemay require maintenance or service at some time. Stopping jobs mayinclude stopping jobs in progress, and/or stopping jobs in queue. Jobsmay be stopped, and/or jobs may be re-routed or otherwise assigned to adifferent device or user, for example, in connection with maintenance orservice having been scheduled for such device, and/or in connection witha triggering event as discussed in more detail below. A standby devicemay be requested to be introduced into a workflow environment, forexample, to provide additional capacity to meet output requirements,and/or to replace a workflow device. A standby device may take the placeof a workflow device, for example, in response to detecting a deviationfrom a parameter value with respect to the workflow device, and/or inresponse to a triggering event as discussed in more detail below. Astandby device may be configured as discussed in more detail below.

In some embodiments, device instructions may be directed towardsforward-looking activities, such as may be associated with deploying anew fleet of devices having a configuration tailored to givenperformance objectives. Alternatively, or in addition, deviceinstructions may be directed towards backwards-looking activities, suchas may be associated with making changes to a fleet of devices based onpast performance of other devices in order to better meet givenperformance objectives. Further, device instructions may be directedtowards real-time management of a fleet of devices, such as may beassociated with managing performance objectives. At least the types ofdevice instructions disclosed herein may be directed towards any suchforward-looking, backwards-looking, or real-time management ofperformance objectives. Further types of device information will beapparent to those skilled in the art.

Fleet Management

Performance objectives for a device or a fleet of devices, for example,resizing on a device network may be managed utilizing one or moreaspects of the systems and methods disclosed herein, including any oneor more steps or features configured for: acquiring device information802, analyzing device information 804, and sending device instructionsbased on device information 806.

With reference to FIG. 9, a schematic is shown, depicting an exemplarydevice network 900. As shown, the exemplary device network 900 mayinclude one or more workflow environments, such as a first workflowenvironment 902 and a second workflow environment 904. The firstworkflow environment includes one or more devices, such as a firstdevice within the first workflow environment 906, a second device withinthe first workflow environment 908, and an N-th device within the firstworkflow environment 910. The second workflow environment also includesone or more devices, such as a first device within the second workflowenvironment 906, a second device within the second workflow environment908, and an N-th device within the second workflow environment 910. Aserver 106 and memory storage 108 also are provided. The server 106 maybe used to manage communications between devices on the device network.Memory storage 108 may be used to store device information. Deviceinformation 802 may be obtained from the first workflow environmentand/or from the second workflow environment. Such device information maypertain to a workflow environment as a whole (e.g., as to all of thedevices in the workflow environment, including workflow devices, andoptionally including standby devices), or such device information maypertain to a subset of devices in the workflow environment (e.g., one ormore workflow devices and/or one or more standby devices). Whenreceiving device information 802, some or all of such device informationmay be stored in memory storage 108. Some or all of the deviceinformation received and/or stored in memory storage may be analyzed 804in accordance with the present disclosure. Analysis may be performedbefore and/or after having stored the device information in memorystorage. Device instructions 806 may be sent to the first workflowenvironment and/or to the second workflow environment. Such deviceinstructions may pertain to a workflow environment as a whole (e.g., asto all of the devices in the workflow environment, including workflowdevices, and optionally including standby devices), or such deviceinstructions may pertain to a subset of devices in the workflowenvironment (e.g., one or more workflow devices and/or one or morestandby devices).

In some embodiments, device information 802 may be obtained from one ormore devices within the first workflow environment (e.g., the firstdevice within the first workflow environment 906), and deviceinstructions 806 may pertain to one or more devices within the firstworkflow environment (e.g., the first device within the first workflowenvironment 906). Alternatively, or in addition, device information 802may be obtained from one or more devices within the first workflowenvironment (e.g., the first device within the first workflowenvironment 906), and device instructions 806 may pertain to one or moredevices within the second workflow environment (e.g., the first devicewithin the first workflow environment 906). In some embodiments, deviceinformation 802 may be obtained from a first device within the firstworkflow environment 906, and device instructions 806 may pertain to thefirst device within the first workflow environment 906. Alternatively,or in addition, device information 802 may be obtained from a firstdevice within the first workflow environment 906, and deviceinstructions 806 may pertain to a second device within the firstworkflow environment 906. Further alternatively, or in further addition,device information 802 may be obtained from a first device within thefirst workflow environment 906, and device instructions 806 may pertainto a first device within the second workflow environment 910.

Schema for managing a device or a fleet of devices may be configured inaccordance with the present disclosure using any combination of thefeatures or steps disclosed herein. Additional combinations will beapparent to the skilled artisan, and are within the spirit and scope ofthe present disclosure. As examples, FIGS. 10A through 10F show variousexemplary schema for managing one or more devices, utilizing exemplarycombinations of various features or steps configured for acquiringdevice information 802, analyzing device information 804, and sendingdevice instructions 806. In one exemplary embodiment 1000 shown in FIG.10A, device information 802 may be acquired from any one or moredevices, which may include a first device 1002 and an N-th device 1004.The device information may include, for example, one or more of theexemplary types of device information shown in FIG. 8C. One or moreaspects of device information 802 are subject to analysis using any oneor more analytical techniques 804. Such analytical techniques mayinclude, for example, one or more of the analytical techniques shown inFIGS. 8D and/or 8E. As shown in FIG. 10A, one or more aspects of deviceinformation are compared to one or more parameters. When a deviationfrom a parameter value has been detected, one or more instructions aresent. When a device network is provided, the one or more instructionsmay be sent to at least one location on the device network. For example,the one or more instructions may be sent to one or more locationsassociated with one or more devices, such as to a location associatedwith the first device 1002 and/or to a location associated with the N-thdevice 1004. The one or more instructions may include, for example, oneor more of the exemplary device instructions shown in FIG. 8F.

In an exemplary embodiment 1000, device information is acquired 802 fromone or more devices. The one or more devices may include a first device1002 and/or one or more additional devices 1004 (e.g., a second device).The first device 1002 and the one or more additional devices 1004 (e.g.,the second device) may be located within the same workflow environmentand enterprise, or the first device may be located in a separateworkflow environment and/or a separate enterprise from the one or moreadditional devices. Further, the one or more additional devices may belocated among one or more workflow environments and/or enterprises. Thedevice information may correspond, for example, to one or more jobshaving been performed or partially performed by the one or more devices.One or more aspects of the device information are compared to one ormore parameter values, and responsive to detecting one or moredeviations from such one or more parameter values, one or moreinstructions are set to one or more locations on a device network. Forexample, an aspect of device information may be compared to a parametervalue (e.g., a first parameter value 1006, a second parameter value1008, a third parameter value 1010, a fourth parameter value 1012, afifth parameter value 1014, and/or an N-th parameter value (not shown)).Responsive to detecting a deviation from a parameter value, one or moreinstructions may be sent to one or more locations on the device network(e.g., a first instruction 1016, a second instruction 1018, a thirdinstruction 1020, a fourth instruction 1022, a fifth instruction 1024,and/or an N-th instruction (not shown)). The one or more instructionsmay trigger one or more actions, which may be responsive to address suchdeviation. As examples, the one or more actions may correspond tocarrying out any device instruction, such as the exemplary deviceinstructions shown in FIG. 8F.

As shown in FIG. 10A, the one or more instructions and corresponding oneor more actions include: stopping a job or jobs 1016, requesting astandby device 1018, re-routing a job or jobs, or otherwise assigning ajob or jobs to a different device or user 1020, scheduling maintenance1022, and/or changing an input parameter, such as a process parameter1024. The location on the device network to which such instructions aresent may be, for example, a location associated with the first device1102 and/or the N-th device 1104. In some embodiments, further deviceinformation may be generated 840, for example, pertaining to any one ormore of the steps of acquiring device information 802, analyzing deviceinformation 804, and sending device instructions 806.

In some embodiments, for example as shown in FIGS. 10B and 10C, deviceinformation associated with a first device 1002 is acquired 802. Thedevice information is analyzed 804, with one or more aspects of thedevice information being compared to one or more parameter values (e.g.,1026 and/or 1028 in FIG. 10B; and/or 1032 and/or 1040 in FIG. 10C), andresponsive to a detecting deviation from a parameter value, one or moreinstructions are respectively sent (e.g., 1027, 1029, and/or 1030 inFIG. 10B; and/or 1033, 1042, 1044, 1046, and/or 1048 in FIG. 10C) to alocation on the device network associated with the first device 1002,triggering action responsive to address the respective deviation.

More particularly, but without limitation, as shown in FIG. 10B, a firstaspect of the device information 802 is compared to a first parametervalue 1026, and responsive to detecting a deviation from the firstparameter value, a first instruction 1027 is sent to at least onelocation on the device network, triggering a first action responsive toaddress such deviation. In some embodiments, as shown in FIG. 10B, thefirst action may comprise scheduling maintenance for the first device.Further, in some embodiments, the first aspect of the device information802 is compared to a second parameter value 1028, and responsive todetecting a deviation from the second parameter value, a secondinstruction 1029 and/or 1030 is sent to at least one location on thedevice network, and/or a third instruction 1029 or 1030 are sent to atleast one location on the device network, triggering a second action,and optionally, a third action responsive to address such deviation. Inaddition, or alternatively, in some embodiments a second aspect of thedevice information may be compared to the first parameter value 1032and/or the second parameter value 1028, similarly triggeringinstructions and corresponding actions responsive to detectingdeviations from parameter values. In some embodiments, as shown in FIG.10B, the second action may comprise stopping one or more jobs assignedto the first device, and the third action may comprise re-routing one ormore jobs from the first device, or otherwise assigning such jobs to adifferent device or user. Alternatively, the second action may compriseboth stopping jobs and re-routing.

Further, as shown in FIG. 10C, a first aspect of the device information802 is compared to a first parameter value 1032, and responsive todetecting a deviation from the first parameter value, a firstinstruction 1033 is sent to at least one location on the device network,triggering a first action responsive to address such deviation. In someembodiments, as shown in FIG. 10C, the first action may comprisechanging an input parameter for the first device. Further, in someembodiments, the first aspect of the device information 802 is comparedto a second parameter value 1034, and responsive to detecting adeviation from the second parameter value, one or more instructions1035, 1036, 1037, and/or 1038 are sent to at least one location on thedevice network, triggering one or more actions responsive to addresssuch deviation. In addition, or alternatively, in some embodiments asecond aspect of the device information may be compared to the firstparameter value 1032 and/or the second parameter value 1034, similarlytriggering one or more instructions and one or more correspondingactions responsive to detecting deviations from parameter values. Insome embodiments, as shown in FIG. 10C, the one or more actions maycomprise: stopping one or more jobs assigned to the first device,requesting a standby device (e.g., to be introduced into the workflowenvironment in place of the first device), re-routing one or more jobsfrom the first device, or otherwise assigning such jobs to a differentdevice or user, and/or scheduling maintenance for the first device.

In another exemplary embodiment, for example a shown in FIG. 10D, one ormore aspects of device information 802 associated with a first device1002 are compared to one or more parameter values 1040, 1041, 1042,1043, and/or 1044, and responsive to detecting a deviation from one ormore of the parameter values, one or more instructions instruction 1045,1046, 1047, 1048, and/or 1049 are sent to at least one location on thedevice network, triggering one or more actions with respect to one ormore additional devices 1004 (e.g., a second device). In yet anotherexemplary embodiment, for example as shown in FIG. 10E, one or moreaspects of the device information 802 associated with the one or moreadditional devices 1004 (e.g. the second device) are compared to one ormore parameter values 1050, 1051, 1052, 1053, and/or 1054, andresponsive to detecting a deviation from one or more of the parametervalues, one or more instructions instruction 1055, 1056, 1057, 1058,and/or 1059 are sent to at least one location on the device network,triggering one or more actions with respect to the first device 1002.

More particularly, but without limitation, in some embodiments forexample as shown in FIG. 10F, device information is acquired 802, andthe device information may be associated with a first device 1002 and/orone or more additional devices 1004 (e.g., a second device). The deviceinformation is analyzed 804, with one or more aspects of the deviceinformation being compared to one or more parameter values (e.g.,1060/1066), and responsive to a detecting deviation from a parametervalue, one or more instructions are respectively sent, triggering actionassociated with the first device 1002 (e.g., 1062, 1067, 1068, 1069,and/or 1070) and/or triggering action associated with the one or moreadditional devices 1004 (e.g., 1064 and/or 1072). The parameter valuesmay be identical or different as between the first device 1002 and theone or more additional devices 1004. For example, as shown in FIG. 10F,a first aspect of device information 802 (which may be based oninformation pertaining to the first device 1002 and/or one or moreadditional devices 1004) is compared to a first parameter value 1060,and responsive to detecting a deviation from the first parameter value,a first instruction is sent to at least one location on the devicenetwork, triggering a first action with respect to the first device 1062and/or with respect to the one or more additional devices 1064. In someembodiments, as shown in FIG. 10F, the first action may comprisechanging an input parameter value for the first device and/or for thesecond device. For example, the instruction triggering changing an inputparameter value 1062 for the first device 1002 may be based oninformation pertaining to the one or more additional devices 1004 (inaddition to, or as an alternative to, information pertaining to thefirst device 1002). Alternatively, or in addition, the instructiontriggering changing an input parameter value 1064 for the one or moreadditional devices 1004 may be based on information pertaining to thefirst device 1002 (in addition to, or as an alternative to, informationpertaining to the one or more additional devices 1004).

Further, in some embodiments, the first aspect of the device information802 (which may be based on information pertaining to the first device1002 and/or one or more additional devices 1004) is compared to one ormore additional parameter values 1066, and responsive to detecting adeviation from one or more of the one or more additional parametervalue, one or more additional instructions are respectively sent to atleast one location on the device network, triggering one or moreadditional actions with respect to the first device 1062 and/or withrespect to the one or more additional devices 1064. In addition, oralternatively, in some embodiments one or more additional aspects ofdevice information may be compared to the first parameter value 1060and/or to the one or more additional parameter values 1066, similarlytriggering instructions and corresponding actions responsive todetecting deviations from parameter values. In some embodiments, the oneor more additional actions may include: stopping one or more jobs,requesting a standby device, re-routing one or more jobs or otherwiseassigning jobs to a different device or user, and/or schedulingmaintenance, in each case with respect to the first device 1062 and/orwith respect to the one or more additional devices 1064. As shown inFIG. 10F, with respect to the first device, one or more jobs arestopped, a standby device has been requested, one or more jobs have beenre-routed or otherwise assigned to a different device, and maintenancehas been scheduled; and with respect to one or more additional devices,maintenance has been scheduled. For example, responsive to detecting adeviation from a parameter value 1066 triggering stopping jobs withrespect to a first device 1002, maintenance may be scheduled 1072 forone or more additional devices 1004, thereby causing maintenance to becarried out on the one or more additional devices 1004 based oninformation pertaining to the first device 1002, potentially avoiding afuture stopping of jobs (e.g., because of a device failure, a qualityissue, and/or unplanned maintenance) with respect to the one or moreadditional devices.

In some embodiments, one or more parameter values may be based onpredictive analytics or other analytical techniques disclosed herein.For example, when detecting a deviation from a parameter valuecorresponding to a first device 1002, predictive analytics or otheranalytical techniques in accordance with the present disclosure mayprovide information based upon which instructions may be sent tolocations on the device network associated with one or more otherdevices 1004 (e.g. a second device), thereby triggering actions withrespect to such one or more other devices 1004 based on having detecteda deviation from a parameter value corresponding to the first device1002. Additionally, or in the alternative, when detecting a deviationfrom a parameter value corresponding to the one or more other device1004, predictive analytics or other analytical techniques may provideinformation based upon which instructions may be sent to locations onthe device network associated with the first device 1002, therebytriggering actions with respect to the first device 1002 based on havingdetected a deviation from a parameter value corresponding to the one ormore other devices 1004. Further, in some embodiments, a parameter valueitself (e.g., 1050, et seq.) corresponding to the first device 1002 maybe based on information, predictive analytics, or other analyticaltechniques associated with one or more other devices 1004. Similarly,information, predictive analytics, or other analytical techniquesassociated with the first device 1002 may provide the basis for aparameter value (e.g., 1040, et seq.) corresponding to the one or moreother devices 1004.

In some embodiments, for example, in the schema for managing a device ora fleet of devices shown in FIGS. 10A through 10F, the one or moredevices may include printers and/or scanners. For example, the firstdevice 1002 and/or the one or more additional devices 1004 may comprisea printing assembly configured to produce printed media and/or indicia,and a scanner/verifier assembly configured to obtain device informationpertaining to printed media and/or indicia produced by the printingassembly. In some embodiments, the scanner/verifier assembly may be aninline scanner/verifier. In addition, or alternatively, the one or moredevices may include printers and/or scanners provide as separatedevices. For example, in some embodiments, a first device may be aprinter having an inline scanner, and a second device may be a printerwithout an inline scanner. Alternatively, in some embodiments, a firstdevice may be a printer and a second device may be a scanner.Alternatively, in some embodiments a fleet of devices may be provided inwhich all of the devices are printers having an inline scanner.

In some embodiments, for example, in the schema for managing a device ora fleet of devices shown in FIGS. 10A through 10F, the deviceinformation may correspond to one or more jobs having been performed orpartially performed by one or more devices. For example, the deviceinformation may comprise one or more digital images of printed mediaand/or indicia. The printed media and/or indicia may have been producedby one or more of such devices, and/or the digital images may have beenobtained by one or more of such devices. In some embodiments (forexample, when a device comprises a printer configured to produce printedmedia and/or indicia and an inline scanner configured to obtain deviceinformation pertaining to printed media and/or indicia produced by theprinter), a parameter value may be based on a scan parameter or a gradefor such indicia, such as an overall symbol grade for such indicia. Forexample, a parameter value may be based on a scan parameter or a gradefor printed media and/or indicia produced by a printer (such as anoverall symbol grade for such indicia), and/or any other quality metriccorresponding to the printed media and/or indicia. For example, aquality metric may be based on a value corresponding to or more of:print growth, print shrinkage, ink spread, edge determination, minimumreflectance, symbol contrast, minimum edge contrast, modulation,printing defects, quiet zone, and decodability, cell contrast, cellmodulation, fixed pattern damage, unused error correction, axialnon-uniformity, and grade non-uniformity. Other quality metrics arediscussed herein, and even further quality metrics will be within thecontemplation of the skilled artisan, all of which are within the spiritand scope of the present disclosure.

In some embodiments, a deviation from a parameter value may correspondto one or more jobs having been performed or partially performed by afirst device 1002 (e.g., an output produced by the first device), andresponsive to detecting the deviation, one or more instructions may besent to at least one location on the device network, triggering one ormore actions with respect to one or more additional devices 1004. Forexample, the one or more actions may include re-routing or otherwiseassigning one or more jobs from a second device to a third device 1020from among the one or more additional devices 1065. Additionally, or inthe alternative, the one or more actions may include one or more of:stopping a job or jobs 1016, requesting a standby device 1018,scheduling maintenance 1022, and/or changing an input parameter, such asa process parameter 1024.

In some embodiments, the one or more additional devices 1004 may includea standby device (e.g., FIGS. 3 through 6), and the one or more actionsmay include triggering the standby device to be introduced into aworkflow environment.

Optimizing

Various embodiments of the present disclosure embrace systems andmethods for optimizing a device or a fleet of devices for one or moreperformance objectives, including quality, productivity, and costfactors. Referring back to FIG. 8A, device information pertaining toperformance objectives may be acquired 802, analyzed 804, and provide abasis for sending device instructions 806, all in accordance with thepresent disclosure. In some situations, various performance objectivesmay have an inversely proportional correlation to one another (e.g.,quality vs. cost, quality vs. productivity, productivity vs. cost), suchthat tradeoffs between competing objectives may exist under a certainconfiguration or across a certain range of configurations.Alternatively, in some embodiments various performance objectives mayhave a proportional correlation to one another, such that a combinationof at least two performance objectives may be improved or optimizedcorrespondingly (e.g., without requiring a tradeoff as between theperformance objectives) under a certain configuration or across acertain range of configurations. Accordingly, various embodimentsfurther embrace systems and methods for analyzing and selecting fromamong various alternatives, for example, to optimize a device or a fleetof devices for one or more performance objectives.

In some situations, a given output may be producible with any one ormore different devices. Similarly, in some situations, a given devicemay be configurable according to any one or more different alternatives.Likewise, a workflow environment and/or an enterprise may beconfigurable according to any one or more different alternatives. Thealternatives for a workflow environment configuration include all of thepossible alternative configurations for each of the devices in theworkflow environment. The alternatives for an enterprise configurationinclude all of the possible alternative configurations for each workflowenvironment in the enterprise and all of the possible alternativeconfigurations for each of the devices therein. As examples, suchalternatives may include a selection of component parts, consumables,process parameters, configurations, and settings for a device ordevices. In addition, it will be appreciated that multitude of factorsmay directly or indirectly impact various performance objectives of anenterprise, of a workflow environment, or of one or more individualdevices. Factors that may be relevant include the selection of a deviceor devices, configurations for a device or devices, jobs and/or usersassigned to a device or devices, maintenance schedules, performanceobjectives, and environmental factors such as temperature, humidity,airborne particulates, etc. In some situations, a multitude of differentfactors may be relevant, and/or the magnitude with which variousrelevant factors directly or indirectly impact performance objectivesmay differ as between different devices, as between different workflowenvironments, and/or as between different enterprises. Further, in somesituations, the relevance and/or the magnitude with which variousrelevant factors directly or indirectly impact performance objectivesmay otherwise be unknown apart from carrying out systems and methodsdisclosed herein. In some embodiments, relevant factors may beidentified using analytical techniques as discussed herein.

In an exemplary embodiment, one or more devices having a verificationsystem are provided. For example, devices having a production system 702and a verification system 704 such as those shown in FIGS. 7A through 7Fmay be used. As discussed above, a verification system may be configuredto verify outputs from a device, and in various embodiments frequentverifications may be obtained, up to and including verifying everyoutput from a device. Device information may be acquired from one ormore devices, including device information obtained from devices havinga verification system. Such device information may be analyzed accordingto the present disclosure to optimize for various performanceobjectives.

With reference to FIGS. 11A through 11C, various examples of formulawhich may be utilized when optimizing for performance objectives areshown. As shown in FIG. 11A, in some embodiments, a device or a fleet ofdevices may be optimized for output quality. Output quality from one ormore devices may be analyzed or compared, for example, by producing andverifying outputs under a first series of conditions 1102 and under asecond series of conditions 1104, with the first series of conditions1102 differing from the second series of conditions 1104 by at least onefactor. Device information acquired under the respective conditions maybe analyzed to ascertain any difference in output quality. A multitudeof factors may be relevant, and a multitude of different conditions maybe compared to one another. Similarly, output quality from one or moreworkflow environments may be analyzed or compared, for example, byaggregating output quality information from the devices within theworkflow environment under a first series of conditions 1106 and under asecond series of conditions 1108. Further, output quality from one ormore enterprises may be analyzed or compared, for example, byaggregating output quality information from the workflow environmentswithin the enterprise under a first series of conditions 1110 and undera second series of conditions 1112.

As shown in FIG. 11B, in some embodiments, a device or a fleet ofdevices may be optimized for productivity. Productivity from one or moredevices may be analyzed or compared, for example, by producing andverifying outputs under a first series of conditions 1114 and under asecond series of conditions 1116, with the first series of conditions1114 differing from the second series of conditions 1116 by at least onefactor. Device information acquired under the respective conditions maybe analyzed to ascertain any difference in productivity. A multitude offactors may be relevant, and a multitude of different conditions may becompared to one another. Similarly, productivity from one or moreworkflow environments may be analyzed or compared, for example, byaggregating productivity information from the devices within theworkflow environment under a first series of conditions 1118 and under asecond series of conditions 1120. Further, productivity from one or moreenterprises may be analyzed or compared, for example, by aggregatingproductivity information from the workflow environments within theenterprise under a first series of conditions 1122 and under a secondseries of conditions 1124.

As shown in FIG. 11C, in some embodiments, a device or a fleet ofdevices may be optimized for various cost factors. Costs factorsassociated with one or more devices may be analyzed or compared, forexample, by producing and verifying outputs under a first series ofconditions 1126 and under a second series of conditions 1128, with thefirst series of conditions 1126 differing from the second series ofconditions 1128 by at least one factor. Device information acquiredunder the respective conditions may be analyzed to ascertain anydifference in one or more cost factors. A multitude of factors may berelevant, and a multitude of different conditions may be compared to oneanother. Similarly, cost information from one or more workflowenvironments may be analyzed or compared, for example, by aggregatingcost information from the devices within the workflow environment undera first series of conditions 1130 and under a second series ofconditions 1132. Further, cost information from one or more enterprisesmay be analyzed or compared, for example, by aggregating costinformation from the workflow environments within the enterprise under afirst series of conditions 1134 and under a second series of conditions1136.

In some embodiments, parameter values based on performance objectivesmay be provided. For example, such parameter values may include aquality value, a productivity value, and/or a cost value. Deviceinformation may be analyzed 804 with respect to any such parameter valuebased on a performance objective, and device instructions may be sent806 with the objective of optimizing for one or more performanceobjectives. In exemplary embodiments, device instructions may beoperative to change (i.e., increase or decrease) a parameter value. Forexample, responsive to detecting a deviation from a parameter valuebased on a performance objective corresponding to one or more devices(or one or more workflow environments or enterprises), an inputparameter for one or more devices may be changed. Such change to theinput parameter may be operative to change a quality value, aproductivity value, and/or a cost value. For example, when a deviationfrom a parameter value indicates that a quality value and/or aproductivity value are too low, and/or a cost value is too high, suchdeviation may trigger one or more instructions responsive to thedeviation.

Example input parameters which may be changed or varied (e.g., tooptimize for output quality, productivity, and/or cost) include heatsettings for one or more print elements of a print head and/or printingspeed. Such heat settings and/or printing speed may be changed orvaried, for example, to optimize a scan parameter or a grade for printedmedia and/or indicia, such as an overall symbol grade for such indicia.Those skilled in the art will appreciate that heat settings and/orprinting speed may impact output quality (e.g., various scan parametersand/or the grade for printed media, such as the overall symbol grade forthe indicia), productivity (e.g., production rate, useful life,maintenance/service schedules), and/or cost (e.g., production costs,component/consumables costs, downtime costs, utilization costs, re-workcosts). As such, in some embodiments heat settings and/or printing speedmay be increased or decreased to optimize for output quality,productivity, and/or cost. Heat settings and/or print speed may beincreased or decreased individually or together, and the increasesand/or decreases may be made correspondingly (e.g., increasing both ordecreasing both) or inversely (e.g., increasing one and decreasing theother).

Example components and/or consumables which may be changed or varied(e.g., to optimize for output quality, productivity, and/or cost)include print heads, drums, rollers, toner, ink, printing ribbon,printable medium, and any other replaceable parts or consumable items.Those skilled in the art will appreciate that different componentsand/or consumables and/or combinations thereof may impact output quality(e.g., various scan parameters and/or grade for printed media, such asthe overall symbol grade for the indicia), productivity (e.g., printingspeed, production rate, useful life of components or devices,maintenance/service schedules), and/or cost (e.g., production costs,component/consumables costs, downtime costs, utilization costs, re-workcosts). As such, in some embodiments various components and/orconsumables may be changed or varied to optimize for output quality,productivity, and/or cost.

In some embodiments, a trade-off may exist as between one or more ofoutput quality, productivity, and/or cost. Output quality may bedecreased in favor of increasing productivity and/or reducing cost.Alternatively, productivity may be decreased and/or cost may beincreased, in favor of increasing output quality. As one example,various scan parameters and/or grade for printed media (such as theoverall symbol grade for indicia) may decrease because of a change toone or more parameters such as heat settings and/or print speed (e.g.,while still maintaining an adequate grade (e.g., overall symbol grade)or other output quality parameters), in favor of increased productivityand/or reduced cost resulting from such change. Alternatively, variousscan parameters and/or grade for printed media, such as the overallsymbol grade for indicia, may increase because of a change to one ormore parameters such as heat settings and/or print speed, resulting indecreased productivity and/or increased cost. As another example, acomponent and/or consumable may be exchange for a less expensivealternative, resulting in a decrease to output quality (e.g., whilestill maintaining an adequate grade (e.g., overall symbol grade) orother output quality parameters for printed media and/or indicia), infavor of increased productivity and/or reduced cost resulting from suchchange. Alternatively, a component and/or consumable may be exchange fora more expensive alternative, resulting in an increase to output qualityand/or productivity.

Conversely in some embodiments, various performance objectives (e.g.,output quality, productivity, and/or cost) may have a proportionalcorrelation to one another, such that a combination of at least twoperformance objectives may be improved or optimized correspondingly(e.g., without requiring a tradeoff as between the performanceobjectives) under a certain configuration or across a certain range ofconfigurations. For example, in some embodiments, optimizing forperformance objectives in accordance with the present disclosure mayreveal a combination of input parameters which provide: an increase inquality corresponding with an increase in productivity and/or a decreasein cost; and/or an increase in productivity corresponding with anincrease in productivity and/or a decrease in cost; and/or a decrease incost corresponding with an increase in quality and/or an increase inproductivity.

In some embodiments, selection of a first component or consumable fromamong a plurality of alternatives may be correlated to a performanceobjective associated with a second component or consumable. For example,a selection of a printable medium may yield an increase or decrease inthe useful life of a print head (or other performance objective), or aselection of a print head may yield an increase or decrease in outputquality (or other performance objective), resulting from printing on aselected printable medium. As another example, a selection of a printingribbon or ink may yield an increase or decrease in the useful life of aprint head (or other performance objective), or a selection of a printhead may yield an increase or decrease in output quality (or otherperformance objective), resulting from printing with a selected printingribbon or ink. It will be appreciated that similar correlations may beidentified with respect to any one or more components/consumables,including print heads, drums, rollers, toner, ink, printing ribbon,printable medium, and any other replaceable parts or consumable items.

Quality Assurance

In some embodiments, the systems and methods disclosed herein may beconfigured to address quality assurance matters. For example, deviceinformation pertaining to verifications obtained from one or moredevices, for example one or more devices having a verification system,may be used as evidence as to the nature of the outputs produced bythose devices. Such information may be useful in the event of an issuewith output quality, such as an output failure, a complaint or otherinquiry pertaining to output quality.

With reference to FIG. 12, an exemplary embodiment of steps or featuresconfigured for addressing quality assurance matters is shown. In anexemplary embodiment outputs are produced 1202, outputs are verified1204, and outputs are distributed 1206. In some embodiments, the outputsmay be printed media and/or indicia printed on a printable medium.Device information is stored 802, which in an exemplary embodimentincludes information pertaining to a plurality of verified outputs(e.g., outputs 1 through N). For example, the information pertaining toverified outputs may include digital images of the printed media and/orindicia (e.g., a digital image of each item of printed media and/orindicia 1 through N). Such verifications may be obtained from a devicehaving a verification system, such as a printer having an inlinescanner. As another example, information pertaining to verified outputsmay include device information showing that a device or devices havebeen maintained or services according to a schedule or otherrequirements. Such device information may include maintenance or serviceschedules, requirements, and/or records for a device or devices.Optionally, the device information may be analyzed 804, and optionally,additional device information may be generated 840. Such additionaldevice information also may be stored, for example, in memory storage108. Responsive to receiving an inquiry about an output or outputs 1208(e.g., an inquiry pertaining to output X, where X is selected from amongoutputs 1 through N), device information pertaining to the output oroutputs is retrieved 1210 from memory storage 108. The deviceinformation retrieved may include the verification information obtainedby a verification system. When the output is printed media and/orindicia, the device information retrieved may include a digital image ofthe printed media and/or indicia. The device information retrieved mayalso include maintenance or service information (e.g., schedules,requirements, and/or records). Additionally, the device informationretrieved may include other pertinent information, such as informationabout what device produced the output, its configuration and settings,quality information, and any other pertinent information as the skilledartisan may desire. A response to the inquiry is then provided 1212. Inan exemplary embodiment, a response to an inquiry 1212 may be based ondevice information. For example, a response to an inquiry 1212 may be toprovide device information (optionally including verificationinformation and/or maintenance or service information) as evidence ofthe nature of the output or outputs to which the inquiry pertains. Insome embodiments, the response to the inquiry may be to send deviceinstructions 806 in accordance with the present disclosure. For example,the inquiry 1208 and/or the device information having been retrieved inresponse to the inquiry 1212 may for the basis for sending deviceinstructions 806.

Introducing Standby Devices into Workflow Environments

Various embodiments of the present disclosure embrace systems andmethods for managing a fleet of devices, including systems and methodsfor introducing a standby device into a workflow environment, and forperforming jobs in a workflow environment. With reference to FIG. 13,some embodiments of these systems and methods 1300 may include any oneor more steps or features configured for: ascertaining when a standbydevice is needed, or may become needed, for a job in a workflowenvironment 1302; selecting a standby device from among a plurality ofstandby devices 1304; configuring a standby device for a job in aworkflow environment 1306; and/or introducing a standby device into aworkflow environment 1308.

Triggering Events

Generally, a current or potential need for a standby device may arise atan unexpected or unpredictable time, for example, when a workflow deviceexperiences a failure or when additional capacity is needed to meetunanticipated productivity fluctuations or production requirements in aworkflow environment. However, sometimes a need for a standby device canbe predicted or otherwise known in advance, in which case downtime for aworkflow device can be scheduled. For example, a need for a standbydevice can be triggered when a workflow device has an upcomingmaintenance requirement (e.g., replacement of components that tend towear out), when a service interval becomes due (e.g., clean the device,refill supplies, or recharge batteries), or when fluctuating productionrequirements are pre-planned. Accordingly, in some embodiments one ormore devices on a device network are configured to ascertain atriggering event, indicating a current or potential need for a standbydevice. Such a triggering event may correspond to any one or more eventsindicating a current or potential need for a standby device, includingexpected or unexpected events and predictable or unpredictable needs.

With reference to FIG. 14, exemplary triggering events are shown. Anyone or more triggering events may be utilized with various embodimentsof the methods disclosed herein. The exemplary triggering events shownin FIG. 14 include triggering events ascertained by a workflow device,triggering events ascertained by a standby device, triggering eventscorresponding to an input from a user, and/or triggering eventsascertained by a server. It will be appreciated the various triggeringevents shown in FIG. 14 may be ascertained by either one or more of aworkflow device, a standby device, or a server, and/or may correspond toan input from a user, and such triggering events are not exclusive toany one source. Additionally, other triggering events will beappreciated by those skilled in the art, all of which are within thespirit and scope of the present disclosure.

For example, in some embodiments a triggering event may be ascertainedby a workflow device. The workflow device may then communicate theexistence of the triggering event to one or more standby devices. Asshown in FIG. 14, triggering events ascertained by a standby device mayinclude a change in status, such as a device failure or scheduleddowntime. A device failure may include a general failure or a physicalfailure such as a damaged or worn-out component, a software failure, ora loss of connectivity in respect of another workflow device, a standbydevice, or another device or resource on a device network. Scheduleddowntime may include a maintenance requirement, or a service intervalbecoming due. A loss of connectivity includes both known and unknownreasons for the loss of connectivity.

Additionally, or in the alternative, a triggering event may beascertained by a standby device. A triggering event ascertained by astandby device may include any of the triggering events ascertained by aworkflow device. For example, in some embodiments one or more standbydevices monitor communications sent by one or more workflow devices, andascertain based on that communication that a standby device is needed ormay become needed for a job in the workflow environment. This may alsoinclude ascertaining a loss of connectivity with a workflow device, forexample, as indicated by the workflow device having communicated anoffline status message or from a period of time having gone by withouthaving received a communication from the workflow device. A standbydevice also may ascertain a current or potential need for a standbydevice independently from any communications from other devices, forexample, by calculating a passage of time corresponding to scheduleddowntime for a workflow device, such as a maintenance requirement or aservice interval; or production requirements. Additionally, a standbydevice may ascertain a triggering event based on information from othersources, such as information from a server or information from a userinput. For example, a server may communicate information pertaining toproduction requirements or scheduled downtime for workflow devices.

Additionally, in some embodiments triggering event may correspond to auser input. Such user input may be in the form of pressing a button orotherwise selecting on a user interface, either on a workflow device, astandby device, or any other interface associated with a device network.

A triggering event indicating a current or potential need for a standbydevice may include any one or more of the foregoing examples.Additionally, a triggering event may be based on a wide variety of otherindicators which will be apparent to those skilled in the art in view ofthe present disclosure.

Selecting the Standby Device

In some embodiments, a device network includes a plurality of standbydevices and it will therefore sometimes be necessary to select a standbydevice from among the plurality. The selected standby device can then beconfigured as required and introduced into the workflow environment. Theskilled artisan will appreciate that a standby device may be selectedfrom among a plurality of standby devices based on any one or moreappropriate factors. For example, a standby device may be selected fromamong a plurality of standby devices based on: whether the standbydevice is configurable to perform a job; whether and the extent to whichthe standby device requires configuration (e.g., to install firmware,software/apps, apply settings); whether the standby device is presentlyavailable for use or whether the standby device has been allocated to orreserved for other purposes; a period of time remaining until the devicebecomes due for a maintenance requirement or a service interval or otherscheduled downtime; the age or generation of the device; or otherfactors which may be useful or desirable. In some embodiments, there maybe only a single option from among the plurality of standby devices, forexample, when only one of the standby devices is available or compatiblefor a given job in a workflow environment. Additionally, in someembodiments a device network may have only a single standby device, inwhich case there would be no alternatives to choose from.

The selection of a standby device may be carried out by a user, by aworkflow device, or by a standby device. For example, a user may choosea standby device from a menu of options on a user interface or bypressing a button on a keypad. A user may make such a selection from aworkflow device, the workflow device then communicating such selectionto the selected standby device. Additionally, or alternatively, a usermay select a standby device on a user interface, such as an interfacefor the standby device being selected, an interface for a workflowdevice being removed from the workflow environment, or a separateinterface.

In some embodiments, a workflow device may automatically choose astandby device based on one or more predefined factors, such as thosementioned above. For example, a workflow device may identify thepresence of one or more standby devices on a device network, and thenchoose a standby device from among those identified. In someembodiments, a workflow device may choose a standby device from among aplurality based on the standby device having been designated as aprimary standby device. In some embodiments, a standby device may beselected by a user, for example via a user interface associated with oneor more standby devices. Such a selection by a user may be utilized, forexample, in the event of a loss of connectivity that renders featuresconfigured for automatic selection of a standby device inoperable.

Additionally, or in the alternative, a standby device may ascertain anorder of selection from among a plurality of standby devices, as for anyone or more workflow devices on a device network. Such order ofselection may be based on any one or more predefined factors, such asthose mentioned above. For example, in some embodiments, a first standbydevice may ascertain that it is available and configurable to perform afirst job presently allocated to a first workflow device, and that basedon one or more predefined factors, no other standby devices havepriority with respect to the first job allocated to the first workflowdevice. The first standby device would then self-select whenascertaining a current or potential need with respect to the first joballocated to the first workflow device.

Furthermore, in some embodiments a second standby device may ascertainthat it is available and configurable to perform the first job, and alsoavailable and configurable to perform a second job presently allocatedto a second workflow device, and that based on one or more predefinedfactors, the first standby device has priority over the second standbydevice with respect to the first job allocated to the first workflowdevice, and that the second standby device has priority over the firststandby device with respect to the second job allocated to the secondworkflow device. The second standby device would then self-select whenascertaining a current or potential need with respect to the second job.Additionally, the second standby device would then self-select over thepriority allocated to the first standby device when the second standbydevice ascertains that the first standby device is unavailable (e.g., inthe event of the device being offline or in the event of a devicefailure).

In some embodiments, a device network having a plurality of standbydevices may include a primary standby device and at least one additionalstandby device, and the primary standby device may select a standbydevice from among the plurality, to be introduced into the workflowenvironment, based on any one or more factors disclosed herein. Forexample, a device network may include a first standby device, a secondstandby device, and a third standby device, in which the first standbydevice has been designated the primary standby device. The primarystandby device may select the second standby device over the thirdstandby device, such that the second standby device would be introducedinto the workflow environment. In addition, or alternatively, theprimary standby device may self-select, such that the primary standbydevice itself would be introduced into the workflow environment over thesecond standby device and the third standby device. Further, a standbydevice may be selected by a user (e.g., via a user interface associatedwith one or more standby devices), for example, in the event of a lossof connectivity that renders features configured for automatic selectionof a standby device inoperable. The selection may be based on any one ormore considerations, such as what jobs have been assigned to therespective devices and which of the devices are configurable to performthose jobs, performance objectives such as output quality, productivity,or cost associated with respective devices, or other considerations inaccordance with the present disclosure. Other considerations will beapparent to those skilled in the art.

In some embodiments, a standby device may be selected in advance, priorto a triggering event, to be introduced into a workflow environment uponthe occurrence of a given triggering event. For example, as shown inFIG. 4, a first standby device 412 shows as being available for all ofthe workflow devices 400 on the device network, and as such has beendesignated as the primary standby device. Accordingly, when a triggeringevent occurs with respect to the device network 400 of FIG. 4, the firststandby device 400 will be selected. As shown in FIG. 5, a first standbydevice 512 shows as being available for workflow devices 1-100, and assuch has been designated as the primary standby device as to thosedevices; and a second standby device 514 shows as being available forworkflow devices 101-250, and as such has been designated as the primarystandby device as to those devices. Accordingly, the device network 500of FIG. 5, the first standby device 512 will be selected when atriggering event occurs with respect to one of workflow devices 1-100,and the second standby device 514 will be selected when a triggeringevent occurs with respect to one of workflow devices 101-250.

Configuring the Standby Device

In some embodiments, a standby device may require configuration beforeintroducing the standby device into a workflow environment.Configuration may include installing firmware, installingsoftware/applications, and/or configuring settings of the standbydevice. For example, a standby device may have a configuration thatdiffers from what is required or preferred to carry out a job in aworkflow environment, and/or from what is required or preferred by auser. In such instances the standby device can be configuredaccordingly. Generally, configuring a standby device includes applying aconfiguration to the standby device according to requirements orpreferences corresponding to a job in a workflow environment and/or auser profile. In some embodiments, configuring a standby device includesreplicating a workflow device on a standby device, for example,configuring the standby device so that the standby device and theworkflow device each have the same version of firmware, software, and/orapplication, and/or the same settings and/or user profile. Additionally,or in the alternative, configuring a standby device also may includeapplying a configuration to a standby device so that the standby devicewill be operable to perform a job in a workflow environment, such as ajob assigned to the workflow device.

In some embodiments, it may be infeasible to replicate a workflow deviceon a standby device. For example, a workflow device may have aconfiguration which is incompatible with the standby device, but in someof those instances there may be a different configuration whereby thestandby device would be operable to perform a job assigned to theworkflow device. This may occur, for example, when a standby device isnot backwards-compatible with a workflow device, but the standby devicemay nevertheless be configurable for a job in the workflow environment.Conversely, in some embodiments, a standby device may already have aconfiguration that accords to requirements or preferences correspondingto a job in a workflow environment and/or a user profile. For example, astandby device may have been previously configured, and in someinstances, introduced into a workflow environment and then subsequentlyreturned to standby status, or a standby device may have beenpre-configured prior to having been introduced to standby status.

In some embodiments, a standby device has a default configuration. Thedefault configuration may be selected by the skilled artisan, forexample, to accommodate one or more configurations of workflow devices.The default configuration may be selected to allow the standby device tobe introduced into a workflow environment in place of a maximum oroptimum number of workflow devices having different configurations. Thedefault configuration also may correspond to a configuration of aworkflow device, for example, when a plurality of workflow devices isprovided, each having a configuration that is the same or similar to oneanother, a standby device may be provided with a default configurationcorresponding to such configuration of the plurality of workflowdevices. The default configuration may be a replica of the configurationapplied to one or more workflow devices, and/or a configurationotherwise according to requirements or preferences corresponding to ajob in a workflow environment and/or a user profile.

When a standby device has a default configuration corresponds to some,but not all, of a plurality of workflow devices with respect to whichthe standby device is available and configurable, the defaultconfiguration can be superseded or overwritten as needed to configurethe standby device accordingly. In some embodiments, a defaultconfiguration may be automatically updated as and when defaults change,for example, to update a standby device configuration with new firmware,software, applications and/or settings as the defaults for those itemschange over time. Example settings may include, for example, settingsassociated with: the device network, one or more devices on a devicenetwork, a workflow, one or more jobs in a workflow, a user, a group ofusers, and/or user preferences. For printers, settings may include, forexample, settings associated with media dimensions, printing quality,printing speed, and/or special printing command languages. For scanners,settings may include, for example, settings associated with interfacecompatibility, symbology, terminal type, control characters, packetmode, access point links, and/or feedback (visual, audible, tactile).Such defaults may be changed over time, for example, to keep the standbydevices up to date with changes in configurations to workflow devices.For example, a standby device may be updated with a new defaultconfiguration so as to correspond to those workflow devices for whichthe standby device has been designated as the primary standby device(e.g., FIGS. 2 and 3), or so that the default configuration wouldcorrespond to the configuration for a majority of workflow devices on adevice network and/or those devices otherwise most likely to invoke atriggering event. Accordingly, in some embodiments a defaultconfiguration may be provided as to one or more standby devices whichcorresponds to a configuration of one or more workflow devices, so thatsuch standby devices will not require configuration (or furtherconfiguration may be minimized) in the event of a triggering eventcorresponding to those workflow devices.

In some embodiments, one or more devices on a device networkautomatically perform all or some of the steps for configuring a standbydevice. In some embodiments, configuration data corresponding to aworkflow device is sent to a standby device. Such configuration data mayinclude a firmware installation file, a software installation file, anapplication installation file, and/or settings information. Theconfiguration data may be sent to a standby device in response to atrigger event, in response to a standby device having ascertained thepresence of new configuration data, in response to the standby devicehaving been selected for a job in a workflow environment, and/or a userinput.

Configuration data corresponding to a workflow device may be housed inmemory storage 108 (FIGS. 1-10). Memory storage 108 may be locatedwithin any one or more of the workflow devices or standby devices on adevice network, and/or may be an external storage device (e.g., externalflash memory) directly connected to any one or more of the workflowdevices or standby devices. Additionally, or in the alternative, memorystorage 108 may be an external storage device accessible on a devicenetwork.

The workflow device may be configured to send configuration data to astandby device, for example, in response to a trigger eventcorresponding to the workflow device, or upon the workflow device havingselected the standby device for a job in a workflow environment, and/ora user input. The standby device may then automatically apply theconfiguration data thereby updating its own configuration and or aconfiguration of another standby device, in each case for example,installing firmware, software, and/or software, and applying settingsaccording to settings information. The standby device may extractconfiguration data from memory storage 108, which may be located withinany one or more of the workflow devices or standby devices on a devicenetwork, and/or may be an external storage device (e.g., external flashmemory) directly connected to any one or more of the workflow devices orstandby devices.

In some embodiments, a first standby device 412 is provided havingmemory storage 108 associated therewith, and housed within the memorystorage is configuration data corresponding to one or more workflowdevices. When a triggering event occurs, the first standby device 412,in this instance designated as the primary standby device, identifies astandby device to be introduced into the workflow environment andconfigures the identified standby device according to the appropriateconfiguration data housed in memory storage. The identified standbydevice may be the first standby device 412 (FIG. 7), or a second standbydevice 414 (not shown). As shown in FIG. 7, the third standby device 416would not be identified for introduction into the workflow environmentin place of the second workflow device 406 because the third standbydevice shows as being available only for workflow devices 26-50, and notthe second workflow device.

With reference to FIG. 15, an exemplary flowchart is shown, depicting asequence of steps for configuring a standby device. The configurationsequence may be commenced 1500 at any time, such as automatically inresponse to a trigger event, in response to a standby device havingascertained the presence of new configuration data, in response to thestandby device having been selected for a job in a workflow environment,and/or in response to a user input. The standby device may be configuredto carry out the configuration sequence autonomously, such as byself-executing installation files.

As shown in FIG. 15, the configuration sequence begins by checking thefirmware 1502. The configuration data may contain multiple instances offirmware which may correspond to different functionalities of thedevice. Each instance of firmware in the configuration data is comparedto the firmware presently installed on the standby device 1504. When aninstance of firmware does not match, the firmware in the configurationdata will be installed on the standby device 1506 and the firmwaresettings will be configured 1508. The configuration sequence proceeds tocheck each instance of software 1510, comparing the software presentlyinstalled on the standby device to the software in the configurationdata 1512. When an instance of software in the configuration data doesnot match the instance installed on the standby device, the instance ofsoftware in the configuration data will be installed 1514, and thesoftware settings will be configured 1516.

The configuration sequence further proceeds to check each application1518, comparing each application presently installed on the standbydevice to the application in the configuration data 1520. When anapplication in the configuration data does not match the applicationinstalled on the standby device, the application in the configurationdata will be installed 1522, and the application settings will beconfigured 1524. The configuration sequence further proceeds to checkmiscellaneous settings (e.g., settings other than firmware settings,software settings, or application settings, already having beenconfigured) 1526, comparing each miscellaneous setting of the standbydevice to the settings information in the configuration data 1528. Whena setting provided for by settings information in the configuration datadoes not match the corresponding setting of the standby device, thesetting will be configured according to the settings information in theconfiguration data 1530. After proceeding through all of installationsand settings, the configuration sequence will end 1532.

Introducing the Standby Device

In some embodiments, a standby device may need to be introduced into aworkflow environment before the standby device begins performing a jobin the workflow environment. With reference to FIG. 16, a standby devicehas been introduced into the workflow environment of FIG. 4 in place ofa workflow device having been removed from the workflow environment. Asshown in FIGS. 4 and 16, a plurality of workflow devices 400 and one ormore of standby devices 402 are provided. A first standby device 412 hasbeen designated as the primary standby device. Alternatively, one of theother standby devices (e.g. a second standby device 414) may bedesignated as the primary standby device (not shown). As shown in FIG.16, the first standby device 412 has been introduced into the workflowenvironment 1600 (with newly assigned identity “Work Flow Device2-SB1”), leaving a standby vacancy 1602. The first standby device hasbeen introduced in place of a workflow device 406 having been removedfrom the workflow environment 1604. A second standby device is thendesignated as the primary standby device, the previous primary standbydevice 412 (i.e., the first standby device) having been introduced intothe workflow environment. In some embodiments, for example, as shown inFIG. 16, a plurality of standby devices may be designated as a primarystandby device, each as to a respective subset of workflow devices on adevice network. As more particularly shown in FIG. 16, a second standbydevice 414, which is shown as being available for workflow devices 1-25(FIG. 4), has now been designated as the primary standby device forworkflow devices 1, 2-SB1, and 3-25 1606, and a third standby device416, which is shown as being available for workflow devices 26-50, hasbeen designated as the primary device for those workflow devices 1608.

In some embodiments, the first standby device 412 may have beenidentified for introduction into the workflow environment by based onits availability for the second workflow device 406. Alternatively, thesecond standby device 414 may have been identified (not shown) as alsobeing available for the second workflow device. A determination asbetween the first standby device and the second standby device may becarried out by the primary standby device, in this case, the firststandby device 412. Alternatively, when the second standby device 414 isdesignated as the primary standby device (not shown), the second standbydevice may identify the first standby device 412 or the second standbydevice 414 for introduction into the workflow environment.

Introducing the first standby device 412 (or alternatively the secondstandby device 414) into the workflow environment may include assigningthe standby device a new IP address corresponding to the job in theworkflow environment. In some embodiments, the standby device 412 may belocated in an area separate from the workflow environment, such as astandby station, and a user may need to physically obtain the standbydevice and bring it to the workflow environment. For example, one ormore standby devices 402, such as printers (e.g., label printers orbarcode printers) or handheld scanners (e.g., RFID scanners or barcodescanners), may be placed on standby status in a convenient locationnearby a workflow environment, such as in a break room. Alternatively,the one or more standby devices 402 may be staged in a workflowenvironment, where the standby devices can immediately begin performinga job upon having been introduced into the workflow environment. Forexample, one or more standby devices 402, such as printers (e.g., labelprinters or barcode printers) or handheld scanners (e.g., RFID scannersor barcode scanners), may be staged on standby status alongside one ormore workflow printers, such that the standby device may beginperforming a job without needing to be physically moved into position ina workflow environment.

In some embodiments, one or more devices on the device networkautomatically perform all or some of the steps for introducing a standbydevice into a workflow environment. For example, a standby device may beconfigured to reboot and assign itself a new IP address corresponding toa job in the workflow environment. In some embodiments, the IP addressmay be assigned by a server 106 (FIGS. 1-9) on the device network. Thestandby device may also be configured to provide an indication to a userthat the standby device has been or is ready to be introduced into theworkflow environment. For example, FIG. 17 shows an exemplary indicationto a user. A plurality of standby devices 1700 is provided, and fromamong the plurality a first standby device 1702 is being introduced intoa workflow environment. The standby device 1702 includes a userinterface 1704, which provides an indication 1706 to the user. Theindication may be configured to provide various information to the user,for example, to inform the user that the standby device is ready forservice, which workflow device the standby device is to replace, and thenew identify for the device in the workflow environment. In someembodiments, the user may simply begin using the standby device in theworkflow environment, or alternatively, a user input may be required tocomplete the process of introducing the standby device into the workflowenvironment such as by moving the device into position.

Managing the Fleet

With reference to FIG. 18, an exemplary method of managing a fleet ofdevices in accordance with the present disclosure is shown. In thisexemplary embodiment, a device network is provided, and residing on thenetwork are a plurality of workflow devices 1800, each having beenassigned a job in a workflow environment, and a one or more standbydevices 1802, each residing on standby to one or more of the workflowdevices. The plurality of workflow devices may each have configurationdata in memory storage, and in some embodiments, the configuration datastored in one workflow device differs in at least one respect fromconfiguration data stored in at least one additional workflow device.The configuration data may include a firmware installation file, asoftware installation file, an application installation file, and/orsettings information. In some embodiments, one or more standby devicesmay be set to standby mode, with a default configuration correspondingto one or more of the plurality of workflow devices. The defaultconfiguration may include firmware, software, applications, and settingscorresponding to a predetermined standby configuration.

In the exemplary embodiment of FIG. 18, a device network includes one ormore workflow devices which are in communication with one or morestandby devices, for example, periodically broadcasting statusinformation to one another 1804. The devices may broadcast statusupdates at any step in the sequence shown in FIG. 18. Optionally,workflow devices may be in communication with one another, and/orstandby devices may be in communication with one another. In someembodiments, one or more standby devices each broadcast statusinformation to at least one of the plurality of workflow devices. Thestatus information may include an identity, a location, and a statusindicating availability of the standby device, e.g., for replicating.For example, the standby devices may broadcast their standby status withtheir unique communications address to the one or more workflow devices,and each workflow device will know of the existence of the one or morestandby devices, and their respective addresses. Where the one or morestandby devices includes a primary standby device as to one or more ofthe workflow devices, the status as a primary standby device will alsobe communicated to at least those workflow devices.

The device network includes a workflow device 1806 and a standby device1808. Optionally, the workflow device 1806 may perform a job in aworkflow environment 1810; however, the sequence in FIG. 18 may alsocommence prior to the workflow device having performed a job. When theworkflow device ascertains a triggering event 1812 (e.g., an exemplarytriggering event from FIG. 14), the workflow device identifies a standbydevice 1808 to be introduced into the workflow environment 1814. In someembodiments, the standby device may be identified based on statusinformation communicated by the one or more standby devices. In someembodiments, the workflow device identifies the standby device over atleast one additional standby device based on a first job having beenassigned to the workflow device, and the standby device has beenidentified as being configurable to perform the first job.

Optionally, the workflow device 1806 or the standby device 1808 mayascertain whether the standby device has a configuration that matchesthe configuration of the workflow device, or whether the standby deviceotherwise requires any configuration data 1816. When the configurationdata matches and/or the standby device does not otherwise require anyconfiguration data, for example, when the standby device configurationis a replica of the workflow device configuration, the standby devicestatus is updated 1824, and the standby device is introduced into theworkflow environment 1828.

When the standby device 1808 has a configuration that does not match theconfiguration of the workflow device, or when the standby deviceotherwise requires some configuration data 1816, the workflow devicethen sends the appropriate configuration data to the standby device1818. Alternatively, when omitting the optional step of ascertainingwhether the standby device has a configuration that matches theconfiguration of the workflow device or whether the standby deviceotherwise requires any configuration data, the workflow device sends theappropriate configuration data to the standby device after the standbydevice has been identified 1814. The configuration data may be sentautomatically in response to the triggering event, or a user mayinitiate the sending of configuration data. Optionally, the step ofsending some or all of the configuration data may be omitted, forexample, when the standby device standby device already has aconfiguration that accords to requirements or preferences correspondingto a job in a workflow environment and/or a user profile, even thoughthe configuration data does not match precisely (not shown). In someembodiments, the configuration data sent to the standby device differsfrom configuration data stored in memory of at least one other workflowdevice from among the plurality. The configuration data may correspondto a first job assigned to the workflow device, and in some embodiments,the first job may differ in at least one respect from a second jobassigned to one of the other workflow devices.

A first job and a second job may be any two jobs. As an example, forprinters, a first job and a second job may include, respectively:printing a first type of labels and printing a second type of labels;printing media for a first production line and printing media for asecond production line; printing as requested by a first user andprinting as requested by a second user. As a further example, forscanners, a first job and a second job may include, respectively:scanning barcodes having a first symbology and scanning barcodes havinga second symbology; scanning materials for a first production line andscanning materials for a second production line; scanning as requestedby a first user and scanning as requested by a second user. Furtherexamples are discussed below.

The standby device receives the configuration data 1820 (e.g., afirmware installation file, a software or application installation file,and/or settings information), optionally communicating to other devicesthat it is no longer available as a standby device to the other workflowdevices(not shown), and then the standby device configures itselfaccordingly 1822, including for example, installing firmware, installingsoftware, installing applications, and/or configuring settings of thestandby device according to settings information. Preferably, followingthe standby device having been configured, the standby device will havea configuration that is a replica of the configuration for the workflowdevice. In some embodiments, the standby device 1808 is configured toperform a job that was assigned to the workflow device 1806.

Upon having been configured, the status of the standby device is updated1824, and optionally, a next standby device is assigned as a primarystandby device 1826. For example, as shown in FIG. 4, the first standbydevice 412 is designated as the primary standby device, and as shown inFIG. 16, has been introduced into the workflow environment. Accordingly,the second standby device 414 and/or the third standby device 416 may bedesignated as a primary standby device (FIG. 16). The standby device1808 is then introduced into the workflow environment 1828, andoptionally, the standby device 1808 may begin performing an assigned jobin the workflow environment 1830, which may include performing the jobassigned to the workflow device 1806, and/or a different job.

In some embodiments, configuration data corresponding to multipledifferent workflow devices and/or multiple workflow devices havingdifferent configurations are housed in memory storage 108 (FIGS. 1-9;not shown in FIG. 18). In some embodiments, the memory storage may be anexternal memory storage device, such as a memory storage device directlyconnected to the standby device 1808. Alternatively, in someembodiments, each standby device may have memory storage 108 housedtherein. In some embodiments, configuration data corresponding tomultiple different workflow devices and/or multiple workflow deviceshaving different configurations may be housed in memory storage of eachof the standby devices. Alternatively, in some embodiments, suchconfiguration data may be transferred or copied to the next standbydevice having been assigned 1826, and/or the memory storage directlyconnected to the standby device 1808 may be disconnected therefrom andthen connected to the next standby device.

Optionally, the standby device 1808 may provide an indication to a user,for example, as shown in FIG. 17. Optionally, the workflow device 1806may be removed from the workflow environment, for example, when thestandby device is introduced into the workflow environment insubstitution for the workflow device.

With reference to FIG. 19, an additional exemplary method of managing afleet of devices in accordance with the present disclosure is shown. Inthis exemplary embodiment, a device network is provided, and residing onthe network are a plurality of workflow devices 1900, each having beenassigned a job in a workflow environment, and a one or more standbydevices 1902, each residing on standby to one or more of the workflowdevices. Optionally, a workflow device may be configured to announce itspresence on the device network and sent its configuration data to behoused in memory storage 108, for example, when the workflow device isfirst added to the device network. The plurality of workflow devices mayeach have configuration data in memory storage, and in some embodiments,the configuration data stored in one workflow device differs in at leastone respect from configuration data stored in at least one additionalworkflow device. The configuration data may include a firmwareinstallation file, a software installation file, an applicationinstallation file, and/or settings information. In some embodiments, oneor more standby devices may be set to standby mode, with a defaultconfiguration corresponding to one or more of the plurality of workflowdevices. The default configuration may include firmware, software,applications, and settings information corresponding to a predeterminedstandby configuration.

Optionally, a workflow device may be configured to identify a standbydevice from among the one or more standby devices 1902 to be introducedinto the workflow environment upon the occurrence of a triggering event.Additionally, or in the alternative, a standby device may be configuredto identify a workflow device from among the plurality of workflowdevices 1900, for which the standby device will serve in a standbycapacity. In some embodiments, a primary standby device may beconfigured to assign one or more other standby devices to serve in astandby capacity to one or more workflow devices.

In the exemplary embodiment of FIG. 19, a device network includes one ormore workflow devices which are in communication with one or morestandby devices, for example, periodically broadcasting statusinformation to one another 1904. The devices may broadcast statusupdates at any step in the sequence shown in FIG. 19. Optionally,workflow devices may be in communication with one another, and/orstandby devices may be in communication with one another. In someembodiments, one or more standby devices each broadcast statusinformation to at least one of the plurality of workflow devices. Thestatus information may include an identity, a location, and a statusindicating availability of the standby device, e.g., for replicating.For example, the standby devices may broadcast their standby status withtheir unique communications address to the one or more workflow devices,and each workflow device will know of the existence of the one or morestandby devices, and their respective addresses. Where the one or morestandby devices includes a primary standby device as to one or more ofthe workflow devices, the status as a primary standby device will alsobe communicated to at least those workflow devices.

As shown in FIG. 19, the device network includes a first workflow device1906 and a first standby device 1908. Optionally, the first standbydevice 1908 may be a primary standby device (FIGS. 4 and 5). In additionto the first standby device 1908, the one or more standby devices 1902may make up a plurality of standby devices 402, 502, 602 (FIGS. 4-6).Optionally, the first workflow device 1906 may perform a job in aworkflow environment 1910; however, the sequence in FIG. 19 may alsocommence prior to the workflow device having performed a job.

In some embodiments, configuration data corresponding to multipledifferent workflow devices and/or multiple workflow devices havingdifferent configurations are housed in memory storage 108 (FIGS. 1-9;not shown in FIG. 19). In some embodiments, the memory storage may be anexternal memory storage device, such as a memory storage device directlyconnected to the first standby device 1908. Alternatively, in someembodiments, each standby device may have memory storage 108 housedtherein. In some embodiments, configuration data corresponding tomultiple different workflow devices and/or multiple workflow deviceshaving different configurations may be housed in memory storage 108.

The first standby device 1908 optionally ascertains whether the firstworkflow device 1906 has any configuration data that is new or that hasbeen changed 1912. In some embodiments, the first standby device 1908,for example a primary standby device as to multiple workflow devices,may ascertain at step 1912 whether any one or more workflow devices haveconfiguration data that is new or that has been changed, and/or whetherany additional workflow devices have been added to the device networkwhich have configuration data not already housed in memory storage 108or which differs from the configuration data in memory storage. Thisstep may optionally be repeated periodically to check for new deviceshaving been added to the device network (e.g., workflow devices and/orstandby devices) and then optionally assign standby devices to workflowdevices accordingly, and/or to check for new configuration data, and/orchanges to configuration data, and then update configuration data housedin memory storage accordingly.

When the presence of a new workflow device and/or new or changedconfiguration data is identified, the first standby device 1908 requeststhe appropriate configuration data 1914 from the appropriate workflowdevice. The requested configuration data may be all of the configurationdata corresponding to the workflow device, or only the configurationdata that is new or has been changed. The workflow device receives therequest for configuration data 1916, and the appropriate configurationdata is sent to the first standby device 1918. The first standby device1908 receives the configuration data 1920, and saves the configurationdata in memory storage 1922, such as memory storage 108. Optionally, thefirst standby device 1918 may configure itself according to the new orchanged configuration data having been received (not shown), forexample, when the new or changed configuration data corresponds to aworkflow device for which the first standby device has been designated aprimary standby device. The first workflow device 1006 may optionallyfurther perform a job in the workflow environment 1924.

In some embodiments, configuration data may be requested automatically1914, and/or configuration data may be sent automatically 1918, inresponse to a triggering event (not shown), or a user may initiate thesending of configuration data (not shown). In some embodiments, theconfiguration data sent to the standby device differs from configurationdata stored in memory of at least one other workflow device from amongthe plurality. The configuration data may correspond to a first jobassigned to the workflow device, and in some embodiments, the first jobmay differ in at least one respect from a second job assigned to one ofthe other workflow devices.

Upon the occurrence of a triggering event 1926, optionally, a standbydevice is identified for introducing into the workflow environment 1928.Alternatively, in some embodiments the standby device to be introducedinto the workflow environment may be predetermined. For example, in someembodiments, the first standby device 1908 will be introduced into theworkflow environment on the occurrence of a triggering event. Thispre-determination may be based, for example, on the first standby devicebeing available to perform a job assigned to the first workflow device1906, and/or by virtue of the first standby device having beendesignated as the primary standby device. It should be noted, however,that the first standby device is not necessarily the primary standbydevice; but rather, in some embodiments, a different standby device maybe designated the primary standby device, and in some embodiments, noneof the standby devices are designated the primary standby device.Alternatively, in some embodiments the standby device to be introducedinto the workflow environment on the occurrence of a triggering eventremains undetermined (not shown), and a standby device will beidentified when a triggering event occurs. In some embodiments, thestandby device may be identified 1928 by the first standby device 1908,which may include self-selecting the first standby device or selecting adifferent standby device from among a plurality of standby devices. Suchidentifying a standby device may be based on status informationcommunicated by the one or more standby devices such as availability ofa standby device as to one or more of the workflow devices, and/orconfiguration information housed in memory storage pertaining toconfigurability of a standby device to perform a job in the workflowenvironment. In some embodiments, the first workflow device 1906 mayidentify a standby device to be introduced into the workflow environmentover at least one additional standby device based on a first job havingbeen assigned to the workflow device, and the standby device has beenidentified as being configurable to perform the first job.

The sequence depicted in FIG. 19 proceeds with optionally ascertainingwhether the standby device to be introduced into the workflowenvironment has a configuration that matches or otherwise is compatiblewith a required configuration, or whether any configuration data isrequired 1930. The required configuration may include a configurationcorresponding to the relevant workflow device, (e.g., the first workflowdevice 1906), and/or a configuration needed to carry out a required jobin the workflow environment. A determination as to whether configurationdata is required may be carried out by the first workflow device 1906and/or by the first standby device 1908. When the configuration datamatches and/or the standby device does not otherwise require anyconfiguration data, for example, when the standby device configurationis a replica of the configuration of the first workflow device 1906, thestandby device status is updated 1936, and the standby device isintroduced into the workflow environment 1940.

When the standby device to be introduced into the workflow environmenthas a configuration that does not match the configuration of theworkflow device, or when the standby device otherwise requires someconfiguration data 1930, the appropriate configuration data is selectedfrom memory storage 1932 (e.g., memory storage 108). The selectedconfiguration data may include, for example, a firmware installationfile, a software installation file, an application installation file,and/or settings information. The selection may be carried out by thefirst standby device 1908 (e.g., when the first standby device 1908 isdesignated as the primary standby device), and/or another standby devicethe plurality (e.g., the standby device to be introduced into theworkflow environment). Alternatively, or in addition, the selection maybe carried out by a user (e.g., via a user interface), for example, inthe event of a loss of connectivity that renders features configured forautomatic selection by a standby device inoperable. Optionally,communications may be transmitted among the devices indicating that thestandby device to be introduced into the workflow environment is nolonger available as a standby device to the other workflow devices (notshown). Alternatively, when omitting the optional step of ascertainingwhether the standby device has a configuration that matches theconfiguration of the workflow device or whether the standby deviceotherwise requires any configuration data, the appropriate configurationis selected from memory storage 1932 (e.g., memory storage 108).

With the appropriate configuration data having been selected from memorystorage, the standby device to be introduced into the workflowenvironment is configured accordingly 1934, including for example,installing firmware, installing software, installing applications,and/or configuring settings of the standby device according to settingsinformation. The standby device so configured may be the first standbydevice 1908 or another standby device on the device network. In someembodiments, the configuration may be carried out by the first standbydevice 1908, or, if different, the standby device to be introduced intothe workflow environment. Preferably, when introducing a standby deviceinto the workflow environment in place of a workflow device, followingthe standby device to be introduced having been configured, such standbydevice will have a configuration that is a replica of the configurationfor the workflow device. In some embodiments, the standby device isconfigured to perform a job that was assigned to the workflow device.

Upon having been configured, the status of the standby device to beintroduced into the workflow environment is updated 1936, andoptionally, when the standby device to be introduced had been a primarystandby device, a next standby device is assigned as a primary standbydevice 1938. For example, as shown in FIG. 4, the first standby device412 is designated as the primary standby device, and as shown in FIG.16, has been introduced into the workflow environment. Accordingly, thesecond standby device 414 and/or the third standby device 416 may bedesignated as a primary standby device (FIG. 16). The first standbydevice 1908 is then introduced into the workflow environment 1040, andoptionally, the first standby device 1908 may begin performing anassigned job in the workflow environment 1942, which may includeperforming the job assigned to the workflow device, and/or a differentjob. In some embodiments, when a next standby device is assigned as aprimary standby device 1938, configuration data in memory storage 108(e.g., memory within the first standby device 1908) may be transferredor copied to additional memory storage 108 corresponding to the nextstandby device having been assigned (e.g., memory within such nextstandby device), and/or memory storage directly connected to the firststandby device 1908 may be disconnected therefrom and then connected tothe next standby device.

Optionally, the first standby device 1908 (and/or another standby devicehaving been identified to be introduced into the workflow environment)may provide an indication to a user, for example, as shown in FIG. 17.Optionally, the first workflow device 1906 may be removed from theworkflow environment, for example, when the standby device is introducedinto the workflow environment in substitution for the workflow device.

Additional Exemplary Devices and Workflow Environments

The present disclosure may utilize any variety of devices orcombinations of devices that may be within the contemplation of thoseskilled in the art. As additional examples, and without limitation, thepresent disclosure may be implemented using one or more of the followingtypes of devices, or combinations thereof: a printer, a barcode scanner,a mobile phone, a computer device (e.g., a desktop, a laptop, a tablet),an RFID device, a wearable device, a copy machine, a fax machine, animage or document scanner, a point-of-sale device an instrument (e.g. ameasurement instrument such as an electronic scale, or a flow meter), acalibration device (e.g., a device for calibrating one or more otherdevices such as instruments), or a dimensioner (e.g., a weighing andvolume measuring system for measuring three-dimensional objects such aspackages, parcels, pallets, cartons, and boxes). A printer may include aprinter with an integrated or in-line scanner/verifier, desktop printer,an “all-in-one” printer, an industrial printer, a mobile printer, abar-code printer, a label printer, a ticket printer, a tag printer, anink-drop printer, a laser printer, a thermal printer, a thermal transferprinter, a 3-D printer, a dot-peen printer, a laser-marking orlaser-engraving printer, an electro-chemical etching printer, a circuitprinter, a point-of-sale device (e.g., a cash register, a paymentconsole, etc.), or any other printer. A barcode scanner may include abarcode verifier, a handheld barcode scanner, a general duty barcodescanner, a healthcare barcode scanner, an in-counter barcode scanner, anindustrial barcode scanner, a hands-free barcode scanner, a pocketbarcode scanner, a wearable barcode scanner (e.g., a hands-free scanningdevice), a point-of-sale device (e.g., a cash register, a paymentconsole, etc.), a dimensioner, or any other scanner. A computer devicemay include a handheld computer, a cold-storage computer, a healthcaremobile computer, a hazardous location computer, a vehicle-mountedcomputer, a wearable computer (e.g., a hands-free computing device). AnRFID device may include an RFID antenna, a RFID reader (e.g., a fixed,desktop, or handheld RFID reader), an RFID printer (e.g., a fixed,desktop, or handheld RFID printer), a vehicle-mounted RFID device (e.g.,an RFID antenna, reader, or printer), or any other RFID device. Awearable device may include a headset, wearable printer, a wearablescanner, or a wearable computer. Devices may include industrial devices,desktop devices, mobile devices. As an example, but without limitation,the foregoing devices may be implemented in various embodiments of thepresent disclosure including a verification system.

As additional examples, and without limitation, a workflow environmentmay include: a warehouse, a distribution center or operation (e.g., aninbound/receiving workflow, a forklift/vehicle workflow, orderfulfillment/picking workflow, and outbound/shipping workflow), amanufacturing facility or operation (e.g., an automated labelingworkflow, a part picking workflow, a part marking workflow, a kittingworkflow, an assembly workflow, an inspection workflow), atransportation facility or operation, a healthcare facility or operation(e.g., an admission workflow, a bedside point-of-care workflow, amedication, surgery, or treatment workflow, a specimen collectionworkflow, a laboratory services workflow, a pharmacy workflow, a medicalsupply tracking workflow), a logistics center or operation, a retaillocation or operation (e.g., a point-of-sale workflow, a customerengagement workflow, a mobile marketing workflow, a store operationsworkflow, a grocery store or grocery workflow, a restaurant orfoodservices location or workflow, a general or specialty retaillocation or workflow), a merchandising and delivery facility oroperation (e.g., a store delivery workflow, a merchandise stockingworkflow, or a home delivery workflow), a government facility oroperation (e.g., a military deployment workflow, a law enforcementworkflow, a public service workflow, a security workflow), a parcelfacility or operation, a courier facility or operation, or a vehicle orvehicle-based operation (e.g., a warehouse vehicle workflow, atransportation vehicle workflow, or a delivery workflow), a port orintermodal facility or operation (e.g., a shipping port or shipping portworkflow, an airport or airport workflow, a bus station or bus stationworkflow, a train station or train station workflow), a field-servicelocation or field operation (e.g., an event location or event managementworkflow, a utilities location or utilities management workflow, a jobsite or job process (e.g., a work order management workflow, a dispatchworkflow, a service route or service workflow, a start of day workflow,a dynamic routing or tracking workflow, an inventory asset managementworkflow, an end of day workflow), a fleet vehicle or rolling stockmanagement facility or operation, a third-party logistics operation orworkflow, and a packaging or labeling facility or operation.

As additional examples, jobs may include printing material, scanningmaterial, receiving a call, initiating a call, transmitting data,receiving data, copying data. As additional examples, jobs may differfrom among one another based any one or more characteristics of therespective jobs. Such differences include different workflows, differentinputs, different outputs, different specifications, different quality,and different users.

To supplement the present disclosure, this application incorporatesentirely by reference the following commonly assigned patents, patentapplication publications, and patent applications:

-   U.S. Pat. Nos. 6,832,725; 7,128,266;-   U.S. Pat. Nos. 7,159,783; 7,413,127;-   U.S. Pat. Nos. 7,726,575; 8,294,969;-   U.S. Pat. Nos. 8,317,105; 8,322,622;-   U.S. Pat. Nos. 8,366,005; 8,371,507;-   U.S. Pat. Nos. 8,376,233; 8,381,979;-   U.S. Pat. Nos. 8,390,909; 8,408,464;-   U.S. Pat. Nos. 8,408,468; 8,408,469;-   U.S. Pat. Nos. 8,424,768; 8,448,863;-   U.S. Pat. Nos. 8,457,013; 8,459,557;-   U.S. Pat. Nos. 8,469,272; 8,474,712;-   U.S. Pat. Nos. 8,479,992; 8,490,877;-   U.S. Pat. Nos. 8,517,271; 8,523,076;-   U.S. Pat. Nos. 8,528,818; 8,544,737;-   U.S. Pat. Nos. 8,548,242; 8,548,420;-   U.S. Pat. Nos. 8,550,335; 8,550,354;-   U.S. Pat. Nos. 8,550,357; 8,556,174;-   U.S. Pat. Nos. 8,556,176; 8,556,177;-   U.S. Pat. Nos. 8,559,767; 8,599,957;-   U.S. Pat. Nos. 8,561,895; 8,561,903;-   U.S. Pat. Nos. 8,561,905; 8,565,107;-   U.S. Pat. Nos. 8,571,307; 8,579,200;-   U.S. Pat. Nos. 8,583,924; 8,584,945;-   U.S. Pat. Nos. 8,587,595; 8,587,697;-   U.S. Pat. Nos. 8,588,869; 8,590,789;-   U.S. Pat. Nos. 8,596,539; 8,596,542;-   U.S. Pat. Nos. 8,596,543; 8,599,271;-   U.S. Pat. Nos. 8,599,957; 8,600,158;-   U.S. Pat. Nos. 8,600,167; 8,602,309;-   U.S. Pat. Nos. 8,608,053; 8,608,071;-   U.S. Pat. Nos. 8,611,309; 8,615,487;-   U.S. Pat. Nos. 8,616,454; 8,621,123;-   U.S. Pat. Nos. 8,622,303; 8,628,013;-   U.S. Pat. Nos. 8,628,015; 8,628,016;-   U.S. Pat. Nos. 8,629,926; 8,630,491;-   U.S. Pat. Nos. 8,635,309; 8,636,200;-   U.S. Pat. Nos. 8,636,212; 8,636,215;-   U.S. Pat. Nos. 8,636,224; 8,638,806;-   U.S. Pat. Nos. 8,640,958; 8,640,960;-   U.S. Pat. Nos. 8,643,717; 8,646,692;-   U.S. Pat. Nos. 8,646,694; 8,657,200;-   U.S. Pat. Nos. 8,659,397; 8,668,149;-   U.S. Pat. Nos. 8,678,285; 8,678,286;-   U.S. Pat. Nos. 8,682,077; 8,687,282;-   U.S. Pat. Nos. 8,692,927; 8,695,880;-   U.S. Pat. Nos. 8,698,949; 8,717,494;-   U.S. Pat. Nos. 8,717,494; 8,720,783;-   U.S. Pat. Nos. 8,723,804; 8,723,904;-   U.S. Pat. Nos. 8,727,223; D702,237;-   U.S. Pat. Nos. 8,740,082; 8,740,085;-   U.S. Pat. Nos. 8,746,563; 8,750,445;-   U.S. Pat. Nos. 8,752,766; 8,756,059;-   U.S. Pat. Nos. 8,757,495; 8,760,563;-   U.S. Pat. Nos. 8,763,909; 8,777,108;-   U.S. Pat. Nos. 8,777,109; 8,779,898;-   U.S. Pat. Nos. 8,781,520; 8,783,573;-   U.S. Pat. Nos. 8,789,757; 8,789,758;-   U.S. Pat. Nos. 8,789,759; 8,794,520;-   U.S. Pat. Nos. 8,794,522; 8,794,525;-   U.S. Pat. Nos. 8,794,526; 8,798,367;-   U.S. Pat. Nos. 8,807,431; 8,807,432;-   U.S. Pat. Nos. 8,820,630; 8,822,848;-   U.S. Pat. Nos. 8,824,692; 8,824,696;-   U.S. Pat. Nos. 8,842,849; 8,844,822;-   U.S. Pat. Nos. 8,844,823; 8,849,019;-   U.S. Pat. Nos. 8,851,383; 8,854,633;-   U.S. Pat. Nos. 8,866,963; 8,868,421;-   U.S. Pat. Nos. 8,868,519; 8,868,802;-   U.S. Pat. Nos. 8,868,803; 8,870,074;-   U.S. Pat. Nos. 8,879,639; 8,880,426;-   U.S. Pat. Nos. 8,881,983; 8,881,987;-   U.S. Pat. Nos. 8,903,172; 8,908,995;-   U.S. Pat. Nos. 8,910,870; 8,910,875;-   U.S. Pat. Nos. 8,914,290; 8,914,788;-   U.S. Pat. Nos. 8,915,439; 8,915,444;-   U.S. Pat. Nos. 8,916,789; 8,918,250;-   U.S. Pat. Nos. 8,918,564; 8,925,818;-   U.S. Pat. Nos. 8,939,374; 8,942,480;-   U.S. Pat. Nos. 8,944,313; 8,944,327;-   U.S. Pat. Nos. 8,944,332; 8,950,678;-   U.S. Pat. Nos. 8,967,468; 8,971,346;-   U.S. Pat. Nos. 8,976,030; 8,976,368;-   U.S. Pat. Nos. 8,978,981; 8,978,983;-   U.S. Pat. Nos. 8,978,984; 8,985,456;-   U.S. Pat. Nos. 8,985,457; 8,985,459;-   U.S. Pat. Nos. 8,985,461; 8,988,578;-   U.S. Pat. Nos. 8,988,590; 8,991,704;-   U.S. Pat. Nos. 8,996,194; 8,996,384;-   U.S. Pat. Nos. 9,002,641; 9,007,368;-   U.S. Pat. Nos. 9,010,641; 9,015,513;-   U.S. Pat. Nos. 9,016,576; 9,022,288;-   U.S. Pat. Nos. 9,030,964; 9,033,240;-   U.S. Pat. Nos. 9,033,242; 9,036,054;-   U.S. Pat. Nos. 9,037,344; 9,038,911;-   U.S. Pat. Nos. 9,038,915; 9,047,098;-   U.S. Pat. Nos. 9,047,359; 9,047,420;-   U.S. Pat. Nos. 9,047,525; 9,047,531;-   U.S. Pat. Nos. 9,053,055; 9,053,378;-   U.S. Pat. Nos. 9,053,380; 9,058,526;-   U.S. Pat. Nos. 9,064,165; 9,064,167;-   U.S. Pat. Nos. 9,064,168; 9,064,254;-   U.S. Pat. Nos. 9,066,032; 9,070,032;-   U.S. Design Pat. No. D716,285;-   U.S. Design Pat. No. D723,560;-   U.S. Design Pat. No. D730,357;-   U.S. Design Pat. No. D730,901;-   U.S. Design Pat. No. D730,902;-   U.S. Design Pat. No. D733,112;-   U.S. Design Pat. No. D734,339;-   International Publication No. 2013/163789;-   International Publication No. 2013/173985;-   International Publication No. 2014/019130;-   International Publication No. 2014/110495;-   U.S. Patent Application Publication No. 2008/0185432;-   U.S. Patent Application Publication No. 2009/0134221;-   U.S. Patent Application Publication No. 2010/0177080;-   U.S. Patent Application Publication No. 2010/0177076;-   U.S. Patent Application Publication No. 2010/0177707;-   U.S. Patent Application Publication No. 2010/0177749;-   U.S. Patent Application Publication No. 2010/0265880;-   U.S. Patent Application Publication No. 2011/0202554;-   U.S. Patent Application Publication No. 2012/0111946;-   U.S. Patent Application Publication No. 2012/0168511;-   U.S. Patent Application Publication No. 2012/0168512;-   U.S. Patent Application Publication No. 2012/0193423;-   U.S. Patent Application Publication No. 2012/0203647;-   U.S. Patent Application Publication No. 2012/0223141;-   U.S. Patent Application Publication No. 2012/0228382;-   U.S. Patent Application Publication No. 2012/0248188;-   U.S. Patent Application Publication No. 2013/0043312;-   U.S. Patent Application Publication No. 2013/0082104;-   U.S. Patent Application Publication No. 2013/0175341;-   U.S. Patent Application Publication No. 2013/0175343;-   U.S. Patent Application Publication No. 2013/0257744;-   U.S. Patent Application Publication No. 2013/0257759;-   U.S. Patent Application Publication No. 2013/0270346;-   U.S. Patent Application Publication No. 2013/0287258;-   U.S. Patent Application Publication No. 2013/0292475;-   U.S. Patent Application Publication No. 2013/0292477;-   U.S. Patent Application Publication No. 2013/0293539;-   U.S. Patent Application Publication No. 2013/0293540;-   U.S. Patent Application Publication No. 2013/0306728;-   U.S. Patent Application Publication No. 2013/0306731;-   U.S. Patent Application Publication No. 2013/0307964;-   U.S. Patent Application Publication No. 2013/0308625;-   U.S. Patent Application Publication No. 2013/0313324;-   U.S. Patent Application Publication No. 2013/0313325;-   U.S. Patent Application Publication No. 2013/0342717;-   U.S. Patent Application Publication No. 2014/0001267;-   U.S. Patent Application Publication No. 2014/0008439;-   U.S. Patent Application Publication No. 2014/0025584;-   U.S. Patent Application Publication No. 2014/0034734;-   U.S. Patent Application Publication No. 2014/0036848;-   U.S. Patent Application Publication No. 2014/0039693;-   U.S. Patent Application Publication No. 2014/0042814;-   U.S. Patent Application Publication No. 2014/0049120;-   U.S. Patent Application Publication No. 2014/0049635;-   U.S. Patent Application Publication No. 2014/0061306;-   U.S. Patent Application Publication No. 2014/0063289;-   U.S. Patent Application Publication No. 2014/0066136;-   U.S. Patent Application Publication No. 2014/0067692;-   U.S. Patent Application Publication No. 2014/0070005;-   U.S. Patent Application Publication No. 2014/0071840;-   U.S. Patent Application Publication No. 2014/0074746;-   U.S. Patent Application Publication No. 2014/0076974;-   U.S. Patent Application Publication No. 2014/0078341;-   U.S. Patent Application Publication No. 2014/0078345;-   U.S. Patent Application Publication No. 2014/0097249;-   U.S. Patent Application Publication No. 2014/0098792;-   U.S. Patent Application Publication No. 2014/0100813;-   U.S. Patent Application Publication No. 2014/0103115;-   U.S. Patent Application Publication No. 2014/0104413;-   U.S. Patent Application Publication No. 2014/0104414;-   U.S. Patent Application Publication No. 2014/0104416;-   U.S. Patent Application Publication No. 2014/0104451;-   U.S. Patent Application Publication No. 2014/0106594;-   U.S. Patent Application Publication No. 2014/0106725;-   U.S. Patent Application Publication No. 2014/0108010;-   U.S. Patent Application Publication No. 2014/0108402;-   U.S. Patent Application Publication No. 2014/0110485;-   U.S. Patent Application Publication No. 2014/0114530;-   U.S. Patent Application Publication No. 2014/0124577;-   U.S. Patent Application Publication No. 2014/0124579;-   U.S. Patent Application Publication No. 2014/0125842;-   U.S. Patent Application Publication No. 2014/0125853;-   U.S. Patent Application Publication No. 2014/0125999;-   U.S. Patent Application Publication No. 2014/0129378;-   U.S. Patent Application Publication No. 2014/0131438;-   U.S. Patent Application Publication No. 2014/0131441;-   U.S. Patent Application Publication No. 2014/0131443;-   U.S. Patent Application Publication No. 2014/0131444;-   U.S. Patent Application Publication No. 2014/0131445;-   U.S. Patent Application Publication No. 2014/0131448;-   U.S. Patent Application Publication No. 2014/0133379;-   U.S. Patent Application Publication No. 2014/0136208;-   U.S. Patent Application Publication No. 2014/0140585;-   U.S. Patent Application Publication No. 2014/0151453;-   U.S. Patent Application Publication No. 2014/0152882;-   U.S. Patent Application Publication No. 2014/0158770;-   U.S. Patent Application Publication No. 2014/0159869;-   U.S. Patent Application Publication No. 2014/0166755;-   U.S. Patent Application Publication No. 2014/0166759;-   U.S. Patent Application Publication No. 2014/0168787;-   U.S. Patent Application Publication No. 2014/0175165;-   U.S. Patent Application Publication No. 2014/0175172;-   U.S. Patent Application Publication No. 2014/0191644;-   U.S. Patent Application Publication No. 2014/0191913;-   U.S. Patent Application Publication No. 2014/0197238;-   U.S. Patent Application Publication No. 2014/0197239;-   U.S. Patent Application Publication No. 2014/0197304;-   U.S. Patent Application Publication No. 2014/0214631;-   U.S. Patent Application Publication No. 2014/0217166;-   U.S. Patent Application Publication No. 2014/0217180;-   U.S. Patent Application Publication No. 2014/0231500;-   U.S. Patent Application Publication No. 2014/0232930;-   U.S. Patent Application Publication No. 2014/0247315;-   U.S. Patent Application Publication No. 2014/0263493;-   U.S. Patent Application Publication No. 2014/0263645;-   U.S. Patent Application Publication No. 2014/0267609;-   U.S. Patent Application Publication No. 2014/0270196;-   U.S. Patent Application Publication No. 2014/0270229;-   U.S. Patent Application Publication No. 2014/0278387;-   U.S. Patent Application Publication No. 2014/0278391;-   U.S. Patent Application Publication No. 2014/0282210;-   U.S. Patent Application Publication No. 2014/0284384;-   U.S. Patent Application Publication No. 2014/0288933;-   U.S. Patent Application Publication No. 2014/0297058;-   U.S. Patent Application Publication No. 2014/0299665;-   U.S. Patent Application Publication No. 2014/0312121;-   U.S. Patent Application Publication No. 2014/0319220;-   U.S. Patent Application Publication No. 2014/0319221;-   U.S. Patent Application Publication No. 2014/0326787;-   U.S. Patent Application Publication No. 2014/0332590;-   U.S. Patent Application Publication No. 2014/0344943;-   U.S. Patent Application Publication No. 2014/0346233;-   U.S. Patent Application Publication No. 2014/0351317;-   U.S. Patent Application Publication No. 2014/0353373;-   U.S. Patent Application Publication No. 2014/0361073;-   U.S. Patent Application Publication No. 2014/0361082;-   U.S. Patent Application Publication No. 2014/0362184;-   U.S. Patent Application Publication No. 2014/0363015;-   U.S. Patent Application Publication No. 2014/0369511;-   U.S. Patent Application Publication No. 2014/0374483;-   U.S. Patent Application Publication No. 2014/0374485;-   U.S. Patent Application Publication No. 2015/0001301;-   U.S. Patent Application Publication No. 2015/0001304;-   U.S. Patent Application Publication No. 2015/0003673;-   U.S. Patent Application Publication No. 2015/0009338;-   U.S. Patent Application Publication No. 2015/0009610;-   U.S. Patent Application Publication No. 2015/0014416;-   U.S. Patent Application Publication No. 2015/0021397;-   U.S. Patent Application Publication No. 2015/0028102;-   U.S. Patent Application Publication No. 2015/0028103;-   U.S. Patent Application Publication No. 2015/0028104;-   U.S. Patent Application Publication No. 2015/0029002;-   U.S. Patent Application Publication No. 2015/0032709;-   U.S. Patent Application Publication No. 2015/0039309;-   U.S. Patent Application Publication No. 2015/0039878;-   U.S. Patent Application Publication No. 2015/0040378;-   U.S. Patent Application Publication No. 2015/0048168;-   U.S. Patent Application Publication No. 2015/0049347;-   U.S. Patent Application Publication No. 2015/0051992;-   U.S. Patent Application Publication No. 2015/0053766;-   U.S. Patent Application Publication No. 2015/0053768;-   U.S. Patent Application Publication No. 2015/0053769;-   U.S. Patent Application Publication No. 2015/0060544;-   U.S. Patent Application Publication No. 2015/0062366;-   U.S. Patent Application Publication No. 2015/0063215;-   U.S. Patent Application Publication No. 2015/0063676;-   U.S. Patent Application Publication No. 2015/0069130;-   U.S. Patent Application Publication No. 2015/0071819;-   U.S. Patent Application Publication No. 2015/0083800;-   U.S. Patent Application Publication No. 2015/0086114;-   U.S. Patent Application Publication No. 2015/0088522;-   U.S. Patent Application Publication No. 2015/0096872;-   U.S. Patent Application Publication No. 2015/0099557;-   U.S. Patent Application Publication No. 2015/0100196;-   U.S. Patent Application Publication No. 2015/0102109;-   U.S. Patent Application Publication No. 2015/0115035;-   U.S. Patent Application Publication No. 2015/0127791;-   U.S. Patent Application Publication No. 2015/0128116;-   U.S. Patent Application Publication No. 2015/0129659;-   U.S. Patent Application Publication No. 2015/0133047;-   U.S. Patent Application Publication No. 2015/0134470;-   U.S. Patent Application Publication No. 2015/0136851;-   U.S. Patent Application Publication No. 2015/0136854;-   U.S. Patent Application Publication No. 2015/0142492;-   U.S. Patent Application Publication No. 2015/0144692;-   U.S. Patent Application Publication No. 2015/0144698;-   U.S. Patent Application Publication No. 2015/0144701;-   U.S. Patent Application Publication No. 2015/0149946;-   U.S. Patent Application Publication No. 2015/0161429;-   U.S. Patent Application Publication No. 2015/0169925;-   U.S. Patent Application Publication No. 2015/0169929;-   U.S. Patent Application Publication No. 2015/0178523;-   U.S. Patent Application Publication No. 2015/0178534;-   U.S. Patent Application Publication No. 2015/0178535;-   U.S. Patent Application Publication No. 2015/0178536;-   U.S. Patent Application Publication No. 2015/0178537;-   U.S. Patent Application Publication No. 2015/0181093;-   U.S. Patent Application Publication No. 2015/0181109;-   U.S. patent application Ser. No. 13/367,978 for a Laser Scanning    Module Employing an Elastomeric U-Hinge Based Laser Scanning    Assembly, filed Feb. 7, 2012 (Feng et al.);-   U.S. Patent Application Ser. No. 29/458,405 for an Electronic    Device, filed Jun. 19, 2013 (Fitch et al.);-   U.S. Patent Application Ser. No. 29/459,620 for an Electronic Device    Enclosure, filed Jul. 2, 2013 (London et al.);-   U.S. Patent Application Ser. No. 29/468,118 for an Electronic Device    Case, filed Sep. 26, 2013 (Oberpriller et al.);-   U.S. patent application Ser. No. 14/150,393 for Indicia-reader    Having Unitary Construction Scanner, filed Jan. 8, 2014 (Colavito et    al.);-   U.S. patent application Ser. No. 14/200,405 for Indicia Reader for    Size-Limited Applications filed Mar. 7, 2014 (Feng et al.);-   U.S. patent application Ser. No. 14/231,898 for Hand-Mounted    Indicia-Reading Device with Finger Motion Triggering filed Apr. 1,    2014 (Van Horn et al.);-   U.S. Patent Application Ser. No. 29/486,759 for an Imaging Terminal,    filed Apr. 2, 2014 (Oberpriller et al.);-   U.S. patent application Ser. No. 14/257,364 for Docking System and    Method Using Near Field Communication filed Apr. 21, 2014    (Showering);-   U.S. patent application Ser. No. 14/264,173 for Autofocus Lens    System for Indicia Readers filed Apr. 29, 2014 (Ackley et al.);-   U.S. patent application Ser. No. 14/277,337 for MULTIPURPOSE OPTICAL    READER, filed May 14, 2014 (Jovanovski et al.);-   U.S. patent application Ser. No. 14/283,282 for TERMINAL HAVING    ILLUMINATION AND FOCUS CONTROL filed May 21, 2014 (Liu et al.);-   U.S. patent application Ser. No. 14/327,827 for a MOBILE-PHONE    ADAPTER FOR ELECTRONIC TRANSACTIONS, filed Jul. 10, 2014 (Hejl);-   U.S. patent application Ser. No. 14/334,934 for a SYSTEM AND METHOD    FOR INDICIA VERIFICATION, filed Jul. 18, 2014 (Hejl);-   U.S. patent application Ser. No. 14/339,708 for LASER SCANNING CODE    SYMBOL READING SYSTEM, filed Jul. 24, 2014 (Xian et al.);-   U.S. patent application Ser. No. 14/340,627 for an AXIALLY    REINFORCED FLEXIBLE SCAN ELEMENT, filed Jul. 25, 2014 (Rueblinger et    al.);-   U.S. patent application Ser. No. 14/446,391 for MULTIFUNCTION POINT    OF SALE APPARATUS WITH OPTICAL SIGNATURE CAPTURE filed Jul. 30, 2014    (Good et al.);-   U.S. patent application Ser. No. 14/452,697 for INTERACTIVE INDICIA    READER, filed Aug. 6, 2014 (Todeschini);-   U.S. patent application Ser. No. 14/453,019 for DIMENSIONING SYSTEM    WITH GUIDED ALIGNMENT, filed Aug. 6, 2014 (Li et al.);-   U.S. patent application Ser. No. 14/462,801 for MOBILE COMPUTING    DEVICE WITH DATA COGNITION SOFTWARE, filed on Aug. 19, 2014    (Todeschini et al.);-   U.S. patent application Ser. No. 14/483,056 for VARIABLE DEPTH OF    FIELD BARCODE SCANNER filed Sep. 10, 2014 (McCloskey et al.);-   U.S. patent application Ser. No. 14/513,808 for IDENTIFYING    INVENTORY ITEMS IN A STORAGE FACILITY filed Oct. 14, 2014 (Singel et    al.);-   U.S. patent application Ser. No. 14/519,195 for HANDHELD    DIMENSIONING SYSTEM WITH FEEDBACK filed Oct. 21, 2014 (Laffargue et    al.);-   U.S. patent application Ser. No. 14/519,179 for DIMENSIONING SYSTEM    WITH MULTIPATH INTERFERENCE MITIGATION filed Oct. 21, 2014 (Thuries    et al.);-   U.S. patent application Ser. No. 14/519,211 for SYSTEM AND METHOD    FOR DIMENSIONING filed Oct. 21, 2014 (Ackley et al.);-   U.S. patent application Ser. No. 14/519,233 for HANDHELD DIMENSIONER    WITH DATA-QUALITY INDICATION filed Oct. 21, 2014 (Laffargue et al.);-   U.S. patent application Ser. No. 14/519,249 for HANDHELD    DIMENSIONING SYSTEM WITH MEASUREMENT-CONFORMANCE FEEDBACK filed Oct.    21, 2014 (Ackley et al.);-   U.S. patent application Ser. No. 14/527,191 for METHOD AND SYSTEM    FOR RECOGNIZING SPEECH USING WILDCARDS IN AN EXPECTED RESPONSE filed    Oct. 29, 2014 (Braho et al.);-   U.S. patent application Ser. No. 14/529,563 for ADAPTABLE INTERFACE    FOR A MOBILE COMPUTING DEVICE filed Oct. 31, 2014 (Schoon et al.);-   U.S. patent application Ser. No. 14/529,857 for BARCODE READER WITH    SECURITY FEATURES filed Oct. 31, 2014 (Todeschini et al.);-   U.S. patent application Ser. No. 14/398,542 for PORTABLE ELECTRONIC    DEVICES HAVING A SEPARATE LOCATION TRIGGER UNIT FOR USE IN    CONTROLLING AN APPLICATION UNIT filed Nov. 3, 2014 (Bian et al.);-   U.S. patent application Ser. No. 14/531,154 for DIRECTING AN    INSPECTOR THROUGH AN INSPECTION filed Nov. 3, 2014 (Miller et al.);-   U.S. patent application Ser. No. 14/533,319 for BARCODE SCANNING    SYSTEM USING WEARABLE DEVICE WITH EMBEDDED CAMERA filed Nov. 5, 2014    (Todeschini) ;-   U.S. patent application Ser. No. 14/535,764 for CONCATENATED    EXPECTED RESPONSES FOR SPEECH RECOGNITION filed Nov. 7, 2014 (Braho    et al.);-   U.S. patent application Ser. No. 14/568,305 for AUTO-CONTRAST    VIEWFINDER FOR AN INDICIA READER filed Dec. 12, 2014 (Todeschini);-   U.S. patent application Ser. No. 14/573,022 for DYNAMIC DIAGNOSTIC    INDICATOR GENERATION filed Dec. 17, 2014 (Goldsmith);-   U.S. patent application Ser. No. 14/578,627 for SAFETY SYSTEM AND    METHOD filed Dec. 22, 2014 (Ackley et al.);-   U.S. patent application Ser. No. 14/580,262 for MEDIA GATE FOR    THERMAL TRANSFER PRINTERS filed Dec. 23, 2014 (Bowles);-   U.S. patent application Ser. No. 14/590,024 for SHELVING AND PACKAGE    LOCATING SYSTEMS FOR DELIVERY VEHICLES filed Jan. 6, 2015 (Payne);-   U.S. patent application Ser. No. 14/596,757 for SYSTEM AND METHOD    FOR DETECTING BARCODE PRINTING ERRORS filed Jan. 14, 2015 (Ackley);-   U.S. patent application Ser. No. 14/416,147 for OPTICAL READING    APPARATUS HAVING VARIABLE SETTINGS filed Jan. 21, 2015 (Chen et    al.);-   U.S. patent application Ser. No. 14/614,706 for DEVICE FOR    SUPPORTING AN ELECTRONIC TOOL ON A USER'S HAND filed Feb. 5, 2015    (Oberpriller et al.);-   U.S. patent application Ser. No. 14/614,796 for CARGO APPORTIONMENT    TECHNIQUES filed Feb. 5, 2015 (Morton et al.);-   U.S. Patent Application Ser. No. 29/516,892 for TABLE COMPUTER filed    Feb. 6, 2015 (Bidwell et al.);-   U.S. patent application Ser. No. 14/619,093 for METHODS FOR TRAINING    A SPEECH RECOGNITION SYSTEM filed Feb. 11, 2015 (Pecorari) ;-   U.S. patent application Ser. No. 14/628,708 for DEVICE, SYSTEM, AND    METHOD FOR DETERMINING THE STATUS OF CHECKOUT LANES filed Feb. 23,    2015 (Todeschini);-   U.S. patent application Ser. No. 14/630,841 for TERMINAL INCLUDING    IMAGING ASSEMBLY filed Feb. 25, 2015 (Gomez et al.);-   U.S. patent application Ser. No. 14/635,346 for SYSTEM AND METHOD    FOR RELIABLE STORE-AND-FORWARD DATA HANDLING BY ENCODED INFORMATION    READING TERMINALS filed Mar. 2, 2015 (Sevier);-   U.S. Patent Application Ser. No. 29/519,017 for SCANNER filed Mar.    2, 2015 (Zhou et al.);-   U.S. patent application Ser. No. 14/405,278 for DESIGN PATTERN FOR    SECURE STORE filed Mar. 9, 2015 (Zhu et al.);-   U.S. patent application Ser. No. 14/660,970 for DECODABLE INDICIA    READING TERMINAL WITH COMBINED ILLUMINATION filed Mar. 18, 2015    (Kearney et al.);-   U.S. patent application Ser. No. 14/661,013 for REPROGRAMMING SYSTEM    AND METHOD FOR DEVICES INCLUDING PROGRAMMING SYMBOL filed Mar. 18,    2015 (Soule et al.);-   U.S. patent application Ser. No. 14/662,922 for MULTIFUNCTION POINT    OF SALE SYSTEM filed Mar. 19, 2015 (Van Horn et al.);-   U.S. patent application Ser. No. 14/663,638 for VEHICLE MOUNT    COMPUTER WITH CONFIGURABLE IGNITION SWITCH BEHAVIOR filed Mar. 20,    2015 (Davis et al.);-   U.S. patent application Ser. No. 14/664,063 for METHOD AND    APPLICATION FOR SCANNING A BARCODE WITH A SMART DEVICE WHILE    CONTINUOUSLY RUNNING AND DISPLAYING AN APPLICATION ON THE SMART    DEVICE DISPLAY filed Mar. 20, 2015 (Todeschini);-   U.S. patent application Ser. No. 14/669,280 for TRANSFORMING    COMPONENTS OF A WEB PAGE TO VOICE PROMPTS filed Mar. 26, 2015    (Funyak et al.);-   U.S. patent application Ser. No. 14/674,329 for AIMER FOR BARCODE    SCANNING filed Mar. 31, 2015 (Bidwell);-   U.S. patent application Ser. No. 14/676,109 for INDICIA READER filed    Apr. 1, 2015 (Huck);-   U.S. patent application Ser. No. 14/676,327 for DEVICE MANAGEMENT    PROXY FOR SECURE DEVICES filed Apr. 1, 2015 (Yeakley et al.);-   U.S. patent application Ser. No. 14/676,898 for NAVIGATION SYSTEM    CONFIGURED TO INTEGRATE MOTION SENSING DEVICE INPUTS filed Apr. 2,    2015 (Showering);-   U.S. patent application Ser. No. 14/679,275 for DIMENSIONING SYSTEM    CALIBRATION SYSTEMS AND METHODS filed Apr. 6, 2015 (Laffargue et    al.);-   U.S. Patent Application Ser. No. 29/523,098 for HANDLE FOR A TABLET    COMPUTER filed Apr. 7, 2015 (Bidwell et al.);-   U.S. patent application Ser. No. 14/682,615 for SYSTEM AND METHOD    FOR POWER MANAGEMENT OF MOBILE DEVICES filed Apr. 9, 2015 (Murawski    et al.);-   U.S. patent application Ser. No. 14/686,822 for MULTIPLE PLATFORM    SUPPORT SYSTEM AND METHOD filed Apr. 15, 2015 (Qu et al.);-   U.S. patent application Ser. No. 14/687,289 for SYSTEM FOR    COMMUNICATION VIA A PERIPHERAL HUB filed Apr. 15, 2015 (Kohtz et    al.);-   U.S. Patent Application Ser. No. 29/524,186 for SCANNER filed Apr.    17, 2015 (Zhou et al.);-   U.S. patent application Ser. No. 14/695,364 for MEDICATION    MANAGEMENT SYSTEM filed Apr. 24, 2015 (Sewell et al.);-   U.S. patent application Ser. No. 14/695,923 for SECURE UNATTENDED    NETWORK AUTHENTICATION filed Apr. 24, 2015 (Kubler et al.);-   U.S. Patent Application Ser. No. 29/525,068 for TABLET COMPUTER WITH    REMOVABLE SCANNING DEVICE filed Apr. 27, 2015 (Schulte et al.);-   U.S. patent application Ser. No. 14/699,436 for SYMBOL READING    SYSTEM HAVING PREDICTIVE DIAGNOSTICS filed Apr. 29, 2015 (Nahill et    al.);-   U.S. patent application Ser. No. 14/702,110 for SYSTEM AND METHOD    FOR REGULATING BARCODE DATA INJECTION INTO A RUNNING APPLICATION ON    A SMART DEVICE filed May 1, 2015 (Todeschini et al.);-   U.S. patent application Ser. No. 14/702,979 for TRACKING BATTERY    CONDITIONS filed May 4, 2015 (Young et al.);-   U.S. patent application Ser. No. 14/704,050 for INTERMEDIATE LINEAR    POSITIONING filed May 5, 2015 (Charpentier et al.);-   U.S. patent application Ser. No. 14/705,012 for HANDS-FREE HUMAN    MACHINE INTERFACE RESPONSIVE TO A DRIVER OF A VEHICLE filed May 6,    2015 (Fitch et al.);-   U.S. patent application Ser. No. 14/705,407 for METHOD AND SYSTEM TO    PROTECT SOFTWARE-BASED NETWORK-CONNECTED DEVICES FROM ADVANCED    PERSISTENT THREAT filed May 6, 2015 (Hussey et al.);-   U.S. patent application Ser. No. 14/707,037 for SYSTEM AND METHOD    FOR DISPLAY OF INFORMATION USING A VEHICLE-MOUNT COMPUTER filed May    8, 2015 (Chamberlin);-   U.S. patent application Ser. No. 14/707,123 for APPLICATION    INDEPENDENT DEX/UCS INTERFACE filed May 8, 2015 (Pape);-   U.S. patent application Ser. No. 14/707,492 for METHOD AND APPARATUS    FOR READING OPTICAL INDICIA USING A PLURALITY OF DATA SOURCES filed    May 8, 2015 (Smith et al.);-   U.S. patent application Ser. No. 14/710,666 for PRE-PAID USAGE    SYSTEM FOR ENCODED INFORMATION READING TERMINALS filed May 13, 2015    (Smith);-   U.S. Patent Application Ser. No. 29/526,918 for CHARGING BASE filed    May 14, 2015 (Fitch et al.);-   U.S. patent application Ser. No. 14/715,672 for AUGUMENTED REALITY    ENABLED HAZARD DISPLAY filed May 19, 2015 (Venkatesha et al.);-   U.S. patent application Ser. No. 14/715,916 for EVALUATING IMAGE    VALUES filed May 19, 2015 (Ackley);-   U.S. patent application Ser. No. 14/722,608 for INTERACTIVE USER    INTERFACE FOR CAPTURING A DOCUMENT IN AN IMAGE SIGNAL filed May 27,    2015 (Showering et al.);-   U.S. Patent Application Ser. No. 29/528,165 for IN-COUNTER BARCODE    SCANNER filed May 27, 2015 (Oberpriller et al.);-   U.S. patent application Ser. No. 14/724,134 for ELECTRONIC DEVICE    WITH WIRELESS PATH SELECTION CAPABILITY filed May 28, 2015 (Wang et    al.);-   U.S. patent application Ser. No. 14/724,849 for METHOD OF    PROGRAMMING THE DEFAULT CABLE INTERFACE SOFTWARE IN AN INDICIA    READING DEVICE filed May 29, 2015 (Barten);-   U.S. patent application Ser. No. 14/724,908 for IMAGING APPARATUS    HAVING IMAGING ASSEMBLY filed May 29, 2015 (Barber et al.);-   U.S. patent application Ser. No. 14/725,352 for APPARATUS AND    METHODS FOR MONITORING ONE OR MORE PORTABLE DATA TERMINALS    (Caballero et al.);-   U.S. Patent Application Ser. No. 29/528,590 for ELECTRONIC DEVICE    filed May 29, 2015 (Fitch et al.);-   U.S. Patent Application Ser. No. 29/528,890 for MOBILE COMPUTER    HOUSING filed Jun. 2, 2015 (Fitch et al.);-   U.S. patent application Ser. No. 14/728,397 for DEVICE MANAGEMENT    USING VIRTUAL INTERFACES CROSS-REFERENCE TO RELATED APPLICATIONS    filed Jun. 2, 2015 (Caballero);-   U.S. patent application Ser. No. 14/732,870 for DATA COLLECTION    MODULE AND SYSTEM filed Jun. 8, 2015 (Powilleit);-   U.S. Patent Application Ser. No. 29/529,441 for INDICIA READING    DEVICE filed Jun. 8, 2015 (Zhou et al.);-   U.S. patent application Ser. No. 14/735,717 for INDICIA-READING    SYSTEMS HAVING AN INTERFACE WITH A USER'S NERVOUS SYSTEM filed Jun.    10, 2015 (Todeschini);-   U.S. patent application Ser. No. 14/738,038 for METHOD OF AND SYSTEM    FOR DETECTING OBJECT WEIGHING INTERFERENCES filed Jun. 12, 2015    (Amundsen et al.);-   U.S. patent application Ser. No. 14/740,320 for TACTILE SWITCH FOR A    MOBILE ELECTRONIC DEVICE filed Jun. 16, 2015 (Bandringa);-   U.S. patent application Ser. No. 14/740,373 for CALIBRATING A VOLUME    DIMENSIONER filed Jun. 16, 2015 (Ackley et al.);-   U.S. patent application Ser. No. 14/742,818 for INDICIA READING    SYSTEM EMPLOYING DIGITAL GAIN CONTROL filed Jun. 18, 2015 (Xian et    al.);-   U.S. patent application Ser. No. 14/743,257 for WIRELESS MESH POINT    PORTABLE DATA TERMINAL filed Jun. 18, 2015 (Wang et al.);-   U.S. Patent Application Ser. No. 29/530,600 for CYCLONE filed Jun.    18, 2015 (Vargo et al);-   U.S. patent application Ser. No. 14/744,633 for IMAGING APPARATUS    COMPRISING IMAGE SENSOR ARRAY HAVING SHARED GLOBAL SHUTTER CIRCUITRY    filed Jun. 19, 2015 (Wang);-   U.S. patent application Ser. No. 14/744,836 for CLOUD-BASED SYSTEM    FOR READING OF DECODABLE INDICIA filed Jun. 19, 2015 (Todeschini et    al.);-   U.S. patent application Ser. No. 14/745,006 for SELECTIVE OUTPUT OF    DECODED MESSAGE DATA filed Jun. 19, 2015 (Todeschini et al.);-   U.S. patent application Ser. No. 14/747,197 for OPTICAL PATTERN    PROJECTOR filed Jun. 23, 2015 (Thuries et al.);-   U.S. patent application Ser. No. 14/747,490 for DUAL-PROJECTOR    THREE-DIMENSIONAL SCANNER filed Jun. 23, 2015 (Jovanovski et al.);    and-   U.S. patent application Ser. No. 14/748,446 for CORDLESS INDICIA    READER WITH A MULTIFUNCTION COIL FOR WIRELESS CHARGING AND EAS    DEACTIVATION, filed Jun. 24, 2015 (Xie et al.).

The foregoing detailed description and accompanying figures set forthtypical embodiments of methods for managing a fleet of devices. Thepresent disclosure is not limited to such exemplary embodiments. It willbe apparent that numerous other methods may be provided. Variousembodiments have been set forth via the use of block diagrams,flowcharts, and/or examples. Insofar as such block diagrams, flowcharts,and/or examples contain one or more functions and/or operations, it willbe understood by those skilled in the art that each function and/oroperation within such block diagrams, flowcharts, or examples can beimplemented, individually and/or collectively, by a wide range ofhardware, software, firmware, or virtually any combination thereof. Inone embodiment, several portions of the subject matter described hereinmay be implemented via Application Specific Integrated Circuits (ASICs),Field Programmable Gate Arrays (FPGAs), digital signal processors(DSPs), or other integrated formats. However, those skilled in the artwill recognize that some aspects and/or features of the embodimentsdisclosed herein, in whole or in part, can be equivalently implementedin integrated circuits, as one or more computer programs running on oneor more computers (e.g., as one or more programs running on one or morecomputer systems), as one or more programs running on one or moreprocessors (e.g., as one or more programs running on one or moremicroprocessors), as firmware, or as virtually any combination thereof,and that designing the circuitry and/or writing the code for thesoftware and or firmware would be well within the skill of one ofordinary skill in the art in light of the present disclosure.

In addition, those skilled in the art will appreciate that themechanisms of the subject matter described herein are capable of beingdistributed as a program product in a variety of forms, and that anillustrative embodiment of the subject matter described herein appliesequally regardless of the particular type of signal bearing media usedto actually carry out the distribution. Examples of a signal bearingmedia include, but are not limited to, the following: recordable typemedia such as volatile and non-volatile memory devices, floppy and otherremovable disks, hard disk drives, SSD drives, flash drives, opticaldiscs (e.g., CD ROMs, DVDs, etc.), and computer memory; and transmissiontype media such as digital and analog communication links using TDM orIP based communication links (e.g., packet links).

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware, orany combination thereof can be viewed as being composed of various typesof “electrical circuitry.” Consequently, as used herein “electricalcircuitry” includes, but is not limited to, electrical circuitry havingat least one discrete electrical circuit, electrical circuitry having atleast one integrated circuit, electrical circuitry having at least oneapplication specific integrated circuit, electrical circuitry forming ageneral purpose computing device configured by a computer program (e.g.,a general purpose computer configured by a computer program which atleast partially carries out processes and/or devices described herein,or a microprocessor configured by a computer program which at leastpartially carries out processes and/or devices described herein),electrical circuitry forming a memory device (e.g., forms of randomaccess memory), and/or electrical circuitry forming a communicationsdevice (e.g., a modem, communications switch, or optical-electricalequipment).

Those skilled in the art will recognize that it is common within the artto describe devices and/or processes in the fashion set forth herein,and thereafter use engineering practices to integrate such describeddevices and/or processes into data processing systems. That is, at leasta portion of the devices and/or processes described herein can beintegrated into a data processing system via a reasonable amount ofexperimentation. Those having skill in the art will recognize that atypical data processing system generally includes one or more of asystem unit housing, a video display device, a memory such as volatileand non-volatile memory, processors such as microprocessors and digitalsignal processors, computational entities such as operating systems,drivers, graphical user interfaces, and applications programs, one ormore interaction devices, such as a touch pad or screen, and/or controlsystems including feedback loops and control elements (e.g., feedbackfor sensing temperature; control heaters for adjusting temperature). Atypical data processing system may be implemented utilizing any suitablecommercially available components, such as those typically found in datacomputing/communication and/or network computing/communication systems.

The foregoing described aspects depict different components containedwithin, or connected with, different other components. It is to beunderstood that such depicted architectures are merely exemplary, andthat in fact many other architectures can be implemented which achievethe same functionality. In a conceptual sense, any arrangement ofcomponents to achieve the same functionality is effectively “associated”such that the desired functionality is achieved. Hence, any twocomponents herein combined to achieve a particular functionality can beseen as “associated with” each other such that the desired functionalityis achieved, irrespective of architectures or intermedial components.Likewise, any two components so associated can also be viewed as being“operably connected”, or “operably coupled”, to each other to achievethe desired functionality. Specific examples of operably couplableinclude but are not limited to physically mateable and/or physicallyinteracting components and/or wirelessly interactable and/or wirelesslyinteracting components and/or logically interacting and/or logicallyinteractable components.

The use of the term “and/or” includes any and all combinations of one ormore of the associated listed items. The figures are schematicrepresentations and so are not necessarily drawn to scale. Unlessotherwise noted, specific terms have been used in a generic anddescriptive sense and not for purposes of limitation.

While various aspects, features, and embodiments have been disclosedherein, other aspects, features, and embodiments will be apparent tothose skilled in the art. The various aspects, features, and embodimentsdisclosed herein are for purposes of illustration and are not intendedto be limiting. It is intended that the scope of the present inventionbe defined by the following claims and their equivalents:

1.-20. (canceled)
 21. A method of managing a fleet of devices, themethod comprising: responsive to a standby device receiving firstconfiguration data from a first workflow device, causing the standbydevice to install firmware in memory of the standby device and/orconfiguring settings of the standby device according to settingsinformation, wherein the first configuration data received by thestandby device differs from second configuration data stored in memoryof a second workflow device; and introducing the standby device into aworkflow environment in substitution for the first workflow device. 22.The method according to claim 21, wherein the fleet of devices compriseone or more standby devices each configured to broadcast statusinformation to at least one of a plurality of workflow devices.
 23. Themethod according to claim 22, wherein the status information comprisesone or more of an identity, a location and a status indicatingavailability of standby device.
 24. The method according to the claim22, further comprising selecting the standby device based at least inpart on the status information.
 25. The method according to claim 21,wherein, prior to causing the standby device to install firmware inmemory of said standby device and/or configuring settings of saidstandby device according to settings information, the method furthercomprises: responsive to a triggering event having occurred with respectto the first workflow device, causing the first configuration data to besent from the first workflow device to the standby device.
 26. Themethod according to claim 25, wherein the triggering event comprisesdetecting one or more of: a device failure, scheduled downtime, aproduction requirement, a loss of connectivity in respect of anotherworkflow device, a deviation from a parameter value, and a user input.27. The method according to claim 21, wherein the fleet of devicesfurther compirses a plurality of workflow devices, each of the pluralityof workflow devices having been assigned a job in the workflowenvironment.
 28. The method according to claim 27, wherein the fleet ofdevices further comprises a plurality of standby devices, each of theplurality of standby devices residing on standby to one or more of theplurality of workflow devices.
 29. A computer program product formanaging a fleet of devices, the computer program product comprising atleast one non-transitory computer-readable storage medium havingcomputer-readable program code portions stored therein, thecomputer-readable program code portions comprising an executable portionconfigured to: responsive to a standby device receiving firstconfiguration data from a first workflow device, cause the standbydevice to install firmware in memory of the standby device and/orconfiguring settings of the standby device according to settingsinformation, wherein the first configuration data received by thestandby device differs from second configuration data stored in memoryof a second workflow device; and introduce the standby device into aworkflow environment in substitution for the first workflow device. 30.The computer program product according to claim 29, wherein the fleet ofdevices comprises one or more standby devices each configured tobroadcast status information to at least one of a plurality of workflowdevices.
 31. The computer program product according to claim 30, whereinthe status information comprises one or more of an identity, a locationand a status indicating availability of standby device.
 32. The computerprogram product according to the claim 30, wherein the computer-readableprogram code portions comprise the executable portion configured toselect the standby device based at least in part on the statusinformation.
 33. The computer program product according to claim 29,wherein, prior to causing the standby device to install firmware inmemory of said standby device and/or configuring settings of saidstandby device according to settings information, the computer-readableprogram code portions comprising the executable portion configured to:responsive to a triggering event having occurred with respect to thefirst workflow device, cause the first configuration data to be sentfrom the first workflow device to the standby device.
 34. The computerprogram product according to claim 33, wherein the triggering eventcomprises detecting one or more of: a device failure, scheduleddowntime, a production requirement, a loss of connectivity in respect ofanother workflow device, a deviation from a parameter value, and a userinput.
 35. An apparatus for managing a fleet of devices, the apparatuscomprising at least one processor and at least one non-transitory memorycomprising program code, the at least one non-transitory memory and theprogram code configured to, with the at least one processor, cause theapparatus to at least: responsive to a standby device receiving firstconfiguration data from a first workflow device, cause the standbydevice to install firmware in memory of the standby device and/orconfiguring settings of the standby device according to settingsinformation, wherein the first configuration data received by thestandby device differs from second configuration data stored in memoryof a second workflow device; and introduce the standby device into aworkflow environment in substitution for the first workflow device. 36.The apparatus according to claim 35, wherein the fleet of devicescomprises one or more standby devices each configured to broadcaststatus information to at least one of a plurality of workflow devices.37. The apparatus according to claim 36, wherein the status informationcomprises one or more of an identity, a location and a status indicatingavailability of standby device.
 38. The apparatus according to the claim36, wherein the at least one non-transitory memory and the program codeare configured to, with the at least one processor, cause the apparatusto select the standby device based at least in part on the statusinformation.
 39. The apparatus according to claim 35, wherein, prior tocausing the standby device to install firmware in memory of said standbydevice and/or configuring settings of said standby device according tosettings information, the at least one non-transitory memory and theprogram code are configured to, with the at least one processor, causethe apparatus to: responsive to a triggering event having occurred withrespect to the first workflow device, cause the first configuration datato be sent from the first workflow device to the standby device.
 40. Theapparatus according to claim 39, wherein the triggering event comprisesdetecting one or more of: a device failure, scheduled downtime, aproduction requirement, a loss of connectivity in respect of anotherworkflow device, a deviation from a parameter value, and a user input.